linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org, adobriyan@gmail.com,
	shakeel.butt@linux.dev, hannes@cmpxchg.org, ak@linux.intel.com,
	osandov@osandov.com, song@kernel.org, jannh@google.com,
	linux-fsdevel@vger.kernel.org, willy@infradead.org
Subject: Re: [PATCH v7 bpf-next 00/10] Harden and extend ELF build ID parsing logic
Date: Wed, 11 Sep 2024 17:10:36 +0000	[thread overview]
Message-ID: <172607463652.988612.1114853675517715254.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240829174232.3133883-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 29 Aug 2024 10:42:22 -0700 you wrote:
> The goal of this patch set is to extend existing ELF build ID parsing logic,
> currently mostly used by BPF subsystem, with support for working in sleepable
> mode in which memory faults are allowed and can be relied upon to fetch
> relevant parts of ELF file to find and fetch .note.gnu.build-id information.
> 
> This is useful and important for BPF subsystem itself, but also for
> PROCMAP_QUERY ioctl(), built atop of /proc/<pid>/maps functionality (see [0]),
> which makes use of the same build_id_parse() functionality. PROCMAP_QUERY is
> always called from sleepable user process context, so it doesn't have to
> suffer from current restrictions of build_id_parse() which are due to the NMI
> context assumption.
> 
> [...]

Here is the summary with links:
  - [v7,bpf-next,01/10] lib/buildid: harden build ID parsing logic
    https://git.kernel.org/bpf/bpf-next/c/905415ff3ffb
  - [v7,bpf-next,02/10] lib/buildid: add single folio-based file reader abstraction
    https://git.kernel.org/bpf/bpf-next/c/de3ec364c3c3
  - [v7,bpf-next,03/10] lib/buildid: take into account e_phoff when fetching program headers
    https://git.kernel.org/bpf/bpf-next/c/d4deb8242341
  - [v7,bpf-next,04/10] lib/buildid: remove single-page limit for PHDR search
    https://git.kernel.org/bpf/bpf-next/c/4e9d360c4cdf
  - [v7,bpf-next,05/10] lib/buildid: rename build_id_parse() into build_id_parse_nofault()
    https://git.kernel.org/bpf/bpf-next/c/45b8fc309654
  - [v7,bpf-next,06/10] lib/buildid: implement sleepable build_id_parse() API
    https://git.kernel.org/bpf/bpf-next/c/ad41251c290d
  - [v7,bpf-next,07/10] lib/buildid: don't limit .note.gnu.build-id to the first page in ELF
    https://git.kernel.org/bpf/bpf-next/c/cdbb44f9a74f
  - [v7,bpf-next,08/10] bpf: decouple stack_map_get_build_id_offset() from perf_callchain_entry
    https://git.kernel.org/bpf/bpf-next/c/4f4c4fc0153f
  - [v7,bpf-next,09/10] bpf: wire up sleepable bpf_get_stack() and bpf_get_task_stack() helpers
    https://git.kernel.org/bpf/bpf-next/c/d4dd9775ec24
  - [v7,bpf-next,10/10] selftests/bpf: add build ID tests
    https://git.kernel.org/bpf/bpf-next/c/3c217a182018

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




      parent reply	other threads:[~2024-09-11 17:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 17:42 Andrii Nakryiko
2024-08-29 17:42 ` [PATCH v7 bpf-next 01/10] lib/buildid: harden " Andrii Nakryiko
2024-11-01 13:54   ` Jiri Olsa
2024-11-01 18:12     ` Andrii Nakryiko
2024-08-29 17:42 ` [PATCH v7 bpf-next 02/10] lib/buildid: add single folio-based file reader abstraction Andrii Nakryiko
2024-08-29 17:42 ` [PATCH v7 bpf-next 03/10] lib/buildid: take into account e_phoff when fetching program headers Andrii Nakryiko
2024-08-29 17:42 ` [PATCH v7 bpf-next 04/10] lib/buildid: remove single-page limit for PHDR search Andrii Nakryiko
2024-08-29 17:42 ` [PATCH v7 bpf-next 05/10] lib/buildid: rename build_id_parse() into build_id_parse_nofault() Andrii Nakryiko
2024-10-14  2:50   ` Lai, Yi
2024-10-14 23:41     ` Andrii Nakryiko
2024-08-29 17:42 ` [PATCH v7 bpf-next 06/10] lib/buildid: implement sleepable build_id_parse() API Andrii Nakryiko
2024-08-29 17:42 ` [PATCH v7 bpf-next 07/10] lib/buildid: don't limit .note.gnu.build-id to the first page in ELF Andrii Nakryiko
2024-08-29 17:42 ` [PATCH v7 bpf-next 08/10] bpf: decouple stack_map_get_build_id_offset() from perf_callchain_entry Andrii Nakryiko
2024-08-29 17:42 ` [PATCH v7 bpf-next 09/10] bpf: wire up sleepable bpf_get_stack() and bpf_get_task_stack() helpers Andrii Nakryiko
2024-11-11  5:51   ` Sergey Senozhatsky
2024-11-11 17:49     ` Andrii Nakryiko
2024-11-12  1:29       ` Sergey Senozhatsky
2024-11-13 20:40         ` Andrii Nakryiko
2024-08-29 17:42 ` [PATCH v7 bpf-next 10/10] selftests/bpf: add build ID tests Andrii Nakryiko
2024-09-03 22:38 ` [PATCH v7 bpf-next 00/10] Harden and extend ELF build ID parsing logic Andrii Nakryiko
2024-09-11  0:27   ` Alexei Starovoitov
2024-09-11 17:10 ` patchwork-bot+netdevbpf [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=172607463652.988612.1114853675517715254.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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@osandov.com \
    --cc=shakeel.butt@linux.dev \
    --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