From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chen Linxuan <chenlinxuan@deepin.org>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Sasha Levin <sashal@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Jann Horn <jannh@google.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Yi Lai <yi1.lai@intel.com>,
Daniel Borkmann <daniel@iogearbox.net>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH stable 6.6] lib/buildid: Handle memfd_secret() files in build_id_parse()
Date: Sun, 16 Mar 2025 07:13:33 +0100 [thread overview]
Message-ID: <2025031645-unsightly-rely-25b3@gregkh> (raw)
In-Reply-To: <6F04B7A95D1A4D64+20250314064039.21110-2-chenlinxuan@deepin.org>
On Fri, Mar 14, 2025 at 02:40:39PM +0800, Chen Linxuan wrote:
> [ Upstream commit 5ac9b4e935dfc6af41eee2ddc21deb5c36507a9f ]
>
> >>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 -EFAULT 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/
>
> Fixes: de3ec364c3c3 ("lib/buildid: add single folio-based file reader abstraction")
> Reported-by: Yi Lai <yi1.lai@intel.com>
> Suggested-by: Shakeel Butt <shakeel.butt@linux.dev>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
> Link: https://lore.kernel.org/bpf/20241017175431.6183-A-hca@linux.ibm.com
> Link: https://lore.kernel.org/bpf/20241017174713.2157873-1-andrii@kernel.org
> [ Linxuan: perform an equivalent direct check without folio-based changes ]
> Fixes: 88a16a130933 ("perf: Add build id data in mmap2 event")
> Signed-off-by: Chen Linxuan <chenlinxuan@deepin.org>
> ---
>
> Some previous discussions can be found in the following links:
> https://lore.kernel.org/stable/05D0A9F7DE394601+20250311100555.310788-2-chenlinxuan@deepin.org/
>
> ---
> lib/buildid.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/lib/buildid.c b/lib/buildid.c
> index 9fc46366597e..6249bd47fb0b 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/secretmem.h>
>
> #define BUILD_ID 3
>
> @@ -157,6 +158,12 @@ int build_id_parse(struct vm_area_struct *vma, unsigned char *build_id,
> if (!vma->vm_file)
> return -EINVAL;
>
> +#ifdef CONFIG_SECRETMEM
> + /* reject secretmem folios created with memfd_secret() */
> + if (vma->vm_file->f_mapping->a_ops == &secretmem_aops)
> + return -EFAULT;
> +#endif
We really do not like #ifdef in .c files. Why can't this use much the
same call it does in the original commit? Just put that in the correct
.h file so that the #ifdef is not needed here, to make the backport
match much more cleanly.
thanks,
greg k-h
next prev parent reply other threads:[~2025-03-16 6:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 6:40 [PATCH stable 6.6] lib/buildid: Handle memfd_secret() files in build_id_parse() Chen Linxuan
2025-03-16 6:13 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-14 9:03 Chen Linxuan
2025-03-14 23:10 ` Sasha Levin
2025-03-11 10:05 Chen Linxuan
2025-03-11 11:14 ` Greg KH
2025-03-12 3:03 ` Chen Linxuan
2025-03-12 18:43 ` Andrii Nakryiko
2025-03-13 16:04 ` Greg KH
2025-03-13 9:01 ` Sasha Levin
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=2025031645-unsightly-rely-25b3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=adobriyan@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenlinxuan@deepin.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=jannh@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=shakeel.butt@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.