From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Andrii Nakryiko <andrii@kernel.org>,
Shaurya Rane <ssrane_b23@ee.vjti.ac.in>,
"Darrick J . Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Meta kernel team <kernel-team@meta.com>,
bpf@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
syzbot+09b7d050e4806540153d@syzkaller.appspotmail.com
Subject: Re: [PATCH] lib/buildid: use __kernel_read() for sleepable context
Date: Thu, 18 Dec 2025 11:51:39 -0800 [thread overview]
Message-ID: <CAEf4BzZrU9xA=S9BFy5MHhmBi_S33yjGWYK1Wx8gs5RdEcjbYQ@mail.gmail.com> (raw)
In-Reply-To: <20251218005818.614819-1-shakeel.butt@linux.dev>
On Wed, Dec 17, 2025 at 4:59 PM Shakeel Butt <shakeel.butt@linux.dev> wrote:
>
> For the sleepable context, convert freader to use __kernel_read()
> instead of direct page cache access via read_cache_folio(). This
> simplifies the faultable code path by using the standard kernel file
> reading interface which handles all the complexity of reading file data.
>
> At the moment we are not changing the code for non-sleepable context
> which uses filemap_get_folio() and only succeeds if the target folios
> are already in memory and up-to-date. The reason is to keep the patch
> simple and easier to backport to stable kernels.
>
> Syzbot repro does not crash the kernel anymore and the selftests run
> successfully.
>
> In the follow up we will make __kernel_read() with IOCB_NOWAIT work for
> non-sleepable contexts. In addition, I would like to replace the
> secretmem check with a more generic approach and will add fstest for the
> buildid code.
>
> Reported-by: syzbot+09b7d050e4806540153d@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=09b7d050e4806540153d
> Fixes: ad41251c290d ("lib/buildid: implement sleepable build_id_parse() API")
> Signed-off-by: Shakeel Butt <shakeel.butt@linux.dev>
> ---
> lib/buildid.c | 47 +++++++++++++++++++++++++++++++++++------------
> 1 file changed, 35 insertions(+), 12 deletions(-)
>
> diff --git a/lib/buildid.c b/lib/buildid.c
> index aaf61dfc0919..e7e258532720 100644
> --- a/lib/buildid.c
> +++ b/lib/buildid.c
> @@ -5,6 +5,7 @@
> #include <linux/elf.h>
> #include <linux/kernel.h>
> #include <linux/pagemap.h>
> +#include <linux/fs.h>
> #include <linux/secretmem.h>
>
> #define BUILD_ID 3
> @@ -37,6 +38,29 @@ static void freader_put_folio(struct freader *r)
> r->folio = NULL;
> }
>
> +/*
> + * Data is read directly into r->buf. Returns pointer to the buffer
> + * on success, NULL on failure with r->err set.
> + */
> +static const void *freader_fetch_sync(struct freader *r, loff_t file_off, size_t sz)
> +{
> + ssize_t ret;
> + loff_t pos = file_off;
> + char *buf = r->buf;
> +
> + do {
> + ret = __kernel_read(r->file, r->buf, sz, &pos);
r->buf -> buf
(and please add [PATCH bpf] for next revision)
pw-bot: cr
> + if (ret <= 0) {
> + r->err = ret ?: -EIO;
> + return NULL;
> + }
> + buf += ret;
> + sz -= ret;
> + } while (sz > 0);
> +
> + return r->buf;
> +}
> +
> static int freader_get_folio(struct freader *r, loff_t file_off)
> {
> /* check if we can just reuse current folio */
> @@ -46,20 +70,9 @@ static int freader_get_folio(struct freader *r, loff_t file_off)
>
> freader_put_folio(r);
>
> - /* reject secretmem folios created with memfd_secret() */
> - if (secretmem_mapping(r->file->f_mapping))
> - return -EFAULT;
> -
> + /* only use page cache lookup - fail if not already cached */
> r->folio = filemap_get_folio(r->file->f_mapping, file_off >> PAGE_SHIFT);
>
> - /* if sleeping is allowed, wait for the page, if necessary */
> - if (r->may_fault && (IS_ERR(r->folio) || !folio_test_uptodate(r->folio))) {
> - filemap_invalidate_lock_shared(r->file->f_mapping);
> - r->folio = read_cache_folio(r->file->f_mapping, file_off >> PAGE_SHIFT,
> - NULL, r->file);
> - filemap_invalidate_unlock_shared(r->file->f_mapping);
> - }
> -
> if (IS_ERR(r->folio) || !folio_test_uptodate(r->folio)) {
> if (!IS_ERR(r->folio))
> folio_put(r->folio);
> @@ -97,6 +110,16 @@ const void *freader_fetch(struct freader *r, loff_t file_off, size_t sz)
> return r->data + file_off;
> }
>
> + /* reject secretmem folios created with memfd_secret() */
> + if (secretmem_mapping(r->file->f_mapping)) {
> + r->err = -EFAULT;
> + return NULL;
> + }
> +
> + /* use __kernel_read() for sleepable context */
> + if (r->may_fault)
> + return freader_fetch_sync(r, file_off, sz);
> +
> /* fetch or reuse folio for given file offset */
> r->err = freader_get_folio(r, file_off);
> if (r->err)
> --
> 2.47.3
>
prev parent reply other threads:[~2025-12-18 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 0:58 Shakeel Butt
2025-12-18 5:13 ` Christoph Hellwig
2025-12-18 19:51 ` Andrii Nakryiko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEf4BzZrU9xA=S9BFy5MHhmBi_S33yjGWYK1Wx8gs5RdEcjbYQ@mail.gmail.com' \
--to=andrii.nakryiko@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shakeel.butt@linux.dev \
--cc=ssrane_b23@ee.vjti.ac.in \
--cc=syzbot+09b7d050e4806540153d@syzkaller.appspotmail.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox