From: Jiri Olsa <olsajiri@gmail.com>
To: Chen Linxuan <chenlinxuan@deepin.org>
Cc: Sasha Levin <sashal@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>, Jann Horn <jannh@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH] lib/buildid: Handle memfd_secret() files in build_id_parse()
Date: Thu, 6 Mar 2025 10:42:17 +0100 [thread overview]
Message-ID: <Z8lt-X7yyhjKMTR7@krava> (raw)
In-Reply-To: <0E394E84CB1C5456+20250306050701.314895-1-chenlinxuan@deepin.org>
On Thu, Mar 06, 2025 at 01:06:58PM +0800, Chen Linxuan wrote:
> Backport of a similar change from commit 5ac9b4e935df ("lib/buildid:
> Handle memfd_secret() files in build_id_parse()") to address an issue
> where accessing secret memfd contents through build_id_parse() would
> trigger faults.
>
> Original report and repro can be found in [0].
>
> [0] https://lore.kernel.org/bpf/ZwyG8Uro%2FSyTXAni@ly-workstation/
>
> This repro will cause BUG: unable to handle kernel paging request in
> build_id_parse in 5.15/6.1/6.6.
hi,
so this patch is meant for one of 5.15/6.1/6.6?
if so you need to send it separately and add that to the subject,
please check Documentation/process/stable-kernel-rules.rst
and you can check other stable kernel patches on the mailing list
like [1][2]
thanks,
jirka
[1] https://lore.kernel.org/bpf/20241206153403.273068-2-daniel@iogearbox.net/
[2] https://lore.kernel.org/bpf/20241104175256.2327164-3-jolsa@kernel.org/
>
> Some other discussions can be found in [1].
>
> [1] https://lore.kernel.org/bpf/20241104175256.2327164-1-jolsa@kernel.org/T/#u
>
> Cc: stable@vger.kernel.org
> Fixes: 88a16a130933 ("perf: Add build id data in mmap2 event")
> Signed-off-by: Chen Linxuan <chenlinxuan@deepin.org>
> ---
> lib/buildid.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/lib/buildid.c b/lib/buildid.c
> index 9fc46366597e..b78d119ed1f7 100644
> --- a/lib/buildid.c
> +++ b/lib/buildid.c
> @@ -157,6 +157,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
> +
> page = find_get_page(vma->vm_file->f_mapping, 0);
> if (!page)
> return -EFAULT; /* page not mapped */
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-03-06 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 5:06 [PATCH] lib/buildid: Handle memfd_secret() files in build_id_parse() Chen Linxuan
2025-03-06 9:42 ` Jiri Olsa [this message]
2025-03-06 19:11 ` Sasha Levin
2025-03-06 23:08 ` Andrew Morton
2025-03-10 3:32 ` Chen Linxuan
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=Z8lt-X7yyhjKMTR7@krava \
--to=olsajiri@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenlinxuan@deepin.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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 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.