From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, linux-mm@kvack.org,
linux-perf-users@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Yi Lai <yi1.lai@intel.com>
Subject: Re: [PATCH bpf] lib/buildid: handle memfd_secret() files in build_id_parse()
Date: Mon, 14 Oct 2024 17:00:08 -0700 [thread overview]
Message-ID: <tvugxgpjgxlospwa2evdsvyjr6k4dkijffrmtgw7rc2gbwrvjz@2nkwwnsmlaum> (raw)
In-Reply-To: <20241014235631.1229438-1-andrii@kernel.org>
On Mon, Oct 14, 2024 at 04:56:31PM GMT, Andrii Nakryiko wrote:
> From memfd_secret(2) manpage:
>
> The memory areas backing the file created with memfd_secret(2) are
> visible only to the processes that have access to the file descriptor.
> The memory region is removed from the kernel page tables and only the
> page tables of the processes holding the file descriptor map the
> corresponding physical memory. (Thus, the pages in the region can't be
> accessed by the kernel itself, so that, for example, pointers to the
> region can't be passed to system calls.)
>
> We need to handle this special case gracefully in build ID fetching
> code. Return -EACCESS whenever secretmem file is passed to build_id_parse()
> family of APIs. Original report and repro can be found in [0].
>
> [0] https://lore.kernel.org/bpf/ZwyG8Uro%2FSyTXAni@ly-workstation/
>
> Reported-by: Yi Lai <yi1.lai@intel.com>
> Suggested-by: Shakeel Butt <shakeel.butt@linux.dev>
> Fixes: de3ec364c3c3 ("lib/buildid: add single folio-based file reader abstraction")
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
next prev parent reply other threads:[~2024-10-15 0:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 23:56 Andrii Nakryiko
2024-10-15 0:00 ` Shakeel Butt [this message]
2024-10-16 18:39 ` Shakeel Butt
2024-10-16 19:59 ` Yosry Ahmed
2024-10-16 21:45 ` Shakeel Butt
2024-10-17 9:17 ` David Hildenbrand
2024-10-17 16:22 ` Shakeel Butt
2024-10-17 17:41 ` David Hildenbrand
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=tvugxgpjgxlospwa2evdsvyjr6k4dkijffrmtgw7rc2gbwrvjz@2nkwwnsmlaum \
--to=shakeel.butt@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=yi1.lai@intel.com \
/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