linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
	 Johannes Weiner <hannes@cmpxchg.org>,
	bpf@vger.kernel.org, linux-mm@kvack.org,
	 akpm@linux-foundation.org, adobriyan@gmail.com,
	ak@linux.intel.com, osandov@osandov.com,  song@kernel.org,
	jannh@google.com, Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH v3 bpf-next 06/10] lib/buildid: implement sleepable build_id_parse() API
Date: Mon, 5 Aug 2024 11:30:13 -0700	[thread overview]
Message-ID: <exs5meqpvcepjd7ymsl4ro6smwirtt3pu5bi3rll7652qftcim@2qdus7b75pff> (raw)
In-Reply-To: <CAEf4BzZ7hGgBeLgLnALM8fuFJw+UqdPPJ4E4a1sAdvWttaBSpw@mail.gmail.com>

On Wed, Jul 31, 2024 at 02:56:00PM GMT, Andrii Nakryiko wrote:
> On Tue, Jul 30, 2024 at 1:39 PM Andrii Nakryiko <andrii@kernel.org> 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 file page into page
> > cache, after which the rest of the logic works just the same at page 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 | 50 ++++++++++++++++++++++++++++++++++----------------
> >  1 file changed, 34 insertions(+), 16 deletions(-)
> >
> > diff --git a/lib/buildid.c b/lib/buildid.c
> > index 5c869a2a30ab..6b5558cd95bf 100644
> > --- a/lib/buildid.c
> > +++ b/lib/buildid.c
> > @@ -20,6 +20,7 @@ struct freader {
> >                         struct page *page;
> >                         void *page_addr;
> >                         u64 file_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)
> > @@ -60,6 +62,17 @@ static int freader_get_page(struct freader *r, u64 file_off)
> >         freader_put_page(r);
> >
> >         r->page = find_get_page(r->mapping, pg_off);
> > +
> > +       if (!r->page && r->may_fault) {
> > +               struct folio *folio;
> > +
> > +               folio = read_cache_folio(r->mapping, pg_off, NULL, NULL);
> > +               if (IS_ERR(folio))
> > +                       return PTR_ERR(folio);
> > +
> > +               r->page = folio_file_page(folio, pg_off);
> > +       }
> > +
> 
> mm folks, is this the sane way to do this? Can you please take a look
> and provide your ack? Thank you!

Yes I think this is sane. I just had to check if read_cache_folio() is
also elevating a reference to the folio similar to find_get_page() and I
think it is doing so. I will go through the series soon.



  reply	other threads:[~2024-08-05 18:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 20:39 [PATCH v3 bpf-next 00/10] Harden and extend ELF build ID parsing logic Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 01/10] lib/buildid: harden " Andrii Nakryiko
2024-07-31  4:04   ` Andi Kleen
2024-07-31 21:54     ` Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 02/10] lib/buildid: add single page-based file reader abstraction Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 03/10] lib/buildid: take into account e_phoff when fetching program headers Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 04/10] lib/buildid: remove single-page limit for PHDR search Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 05/10] lib/buildid: rename build_id_parse() into build_id_parse_nofault() Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 06/10] lib/buildid: implement sleepable build_id_parse() API Andrii Nakryiko
2024-07-31 21:56   ` Andrii Nakryiko
2024-08-05 18:30     ` Shakeel Butt [this message]
2024-07-30 20:39 ` [PATCH v3 bpf-next 07/10] lib/buildid: don't limit .note.gnu.build-id to the first page in ELF Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 08/10] bpf: decouple stack_map_get_build_id_offset() from perf_callchain_entry Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 09/10] bpf: wire up sleepable bpf_get_stack() and bpf_get_task_stack() helpers Andrii Nakryiko
2024-07-30 20:39 ` [PATCH v3 bpf-next 10/10] selftests/bpf: add build ID tests 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=exs5meqpvcepjd7ymsl4ro6smwirtt3pu5bi3rll7652qftcim@2qdus7b75pff \
    --to=shakeel.butt@linux.dev \
    --cc=adobriyan@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=jannh@google.com \
    --cc=linux-mm@kvack.org \
    --cc=osandov@fb.com \
    --cc=osandov@osandov.com \
    --cc=song@kernel.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