From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, adobriyan@gmail.com,
hannes@cmpxchg.org, ak@linux.intel.com, osandov@osandov.com,
song@kernel.org, jannh@google.com,
linux-fsdevel@vger.kernel.org, willy@infradead.org,
Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH v4 bpf-next 06/10] lib/buildid: implement sleepable build_id_parse() API
Date: Thu, 8 Aug 2024 11:40:13 -0700 [thread overview]
Message-ID: <f3iayd76egugsgmk3evwrzn4bcko5ax2nohatgcdyxss2ilwup@pmrkbledcpc3> (raw)
In-Reply-To: <20240807234029.456316-7-andrii@kernel.org>
On Wed, Aug 07, 2024 at 04:40:25PM GMT, Andrii Nakryiko wrote:
> Extend freader with a flag specifying whether it's OK to cause page
> fault to fetch file data that is not already physically present in
> memory. With this, it's now easy to wait for data if the caller is
> running in sleepable (faultable) context.
>
> We utilize read_cache_folio() to bring the desired folio into page
> cache, after which the rest of the logic works just the same at folio level.
>
> Suggested-by: Omar Sandoval <osandov@fb.com>
> Cc: Shakeel Butt <shakeel.butt@linux.dev>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> ---
> lib/buildid.c | 44 ++++++++++++++++++++++++++++----------------
> 1 file changed, 28 insertions(+), 16 deletions(-)
>
> diff --git a/lib/buildid.c b/lib/buildid.c
> index 5e6f842f56f0..e1c01b23efd8 100644
> --- a/lib/buildid.c
> +++ b/lib/buildid.c
> @@ -20,6 +20,7 @@ struct freader {
> struct folio *folio;
> void *addr;
> loff_t folio_off;
> + bool may_fault;
> };
> struct {
> const char *data;
> @@ -29,12 +30,13 @@ struct freader {
> };
>
> static void freader_init_from_file(struct freader *r, void *buf, u32 buf_sz,
> - struct address_space *mapping)
> + struct address_space *mapping, bool may_fault)
> {
> memset(r, 0, sizeof(*r));
> r->buf = buf;
> r->buf_sz = buf_sz;
> r->mapping = mapping;
> + r->may_fault = may_fault;
> }
>
> static void freader_init_from_mem(struct freader *r, const char *data, u64 data_sz)
> @@ -63,6 +65,11 @@ static int freader_get_folio(struct freader *r, loff_t file_off)
> freader_put_folio(r);
>
> r->folio = filemap_get_folio(r->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)))
> + r->folio = read_cache_folio(r->mapping, file_off >> PAGE_SHIFT, NULL, NULL);
Willy's network fs comment is bugging me. If we pass NULL for filler,
the kernel will going to use fs's read_folio() callback. I have checked
read_folio() for fuse and nfs and it seems like for at least these two
filesystems the callback is accessing file->private_data. So, if the elf
file is on these filesystems, we might see null accesses.
next prev parent reply other threads:[~2024-08-08 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240807234029.456316-1-andrii@kernel.org>
[not found] ` <20240807234029.456316-3-andrii@kernel.org>
2024-08-08 18:33 ` [PATCH v4 bpf-next 02/10] lib/buildid: add single folio-based file reader abstraction Shakeel Butt
[not found] ` <20240807234029.456316-7-andrii@kernel.org>
2024-08-08 18:40 ` Shakeel Butt [this message]
2024-08-08 20:15 ` [PATCH v4 bpf-next 06/10] lib/buildid: implement sleepable build_id_parse() API Andrii Nakryiko
2024-08-08 20:57 ` Jann Horn
2024-08-08 21:23 ` Andrii Nakryiko
2024-08-08 21:02 ` Shakeel Butt
2024-08-08 21:21 ` Andrii Nakryiko
[not found] ` <20240807234029.456316-2-andrii@kernel.org>
2024-08-08 22:24 ` [PATCH v4 bpf-next 01/10] lib/buildid: harden build ID parsing logic Andi Kleen
2024-08-08 22:44 ` Andrii Nakryiko
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=f3iayd76egugsgmk3evwrzn4bcko5ax2nohatgcdyxss2ilwup@pmrkbledcpc3 \
--to=shakeel.butt@linux.dev \
--cc=adobriyan@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osandov@fb.com \
--cc=osandov@osandov.com \
--cc=song@kernel.org \
--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