mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chen Linxuan <chenlinxuan@deepin.org>
To: Greg KH <greg@kroah.com>
Cc: Chen Linxuan <chenlinxuan@deepin.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	 Jiri Olsa <jolsa@kernel.org>, Sasha Levin <sashal@kernel.org>,
	 Eduard Zingerman <eddyz87@gmail.com>,
	Jann Horn <jannh@google.com>,
	 Alexey Dobriyan <adobriyan@gmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	 Shakeel Butt <shakeel.butt@linux.dev>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	 Yi Lai <yi1.lai@intel.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	stable@vger.kernel.org,  linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH stable 6.6 v2] lib/buildid: Handle memfd_secret() files in build_id_parse()
Date: Mon, 17 Mar 2025 13:04:41 +0800	[thread overview]
Message-ID: <CAC1kPDNNBj3Hd6s72mA3qxwxC0B69aE7qhM+Az5msvjPy41N5w@mail.gmail.com> (raw)
In-Reply-To: <2025031759-sacrifice-wreckage-9948@gregkh>

Greg KH <greg@kroah.com> 于2025年3月17日周一 12:20写道:
>
> On Mon, Mar 17, 2025 at 09:16:04AM +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
> > [ Chen Linxuan: backport same logic without folio-based changes ]
> > Cc: stable@vger.kernel.org
> > Fixes: 88a16a130933 ("perf: Add build id data in mmap2 event")
> > Signed-off-by: Chen Linxuan <chenlinxuan@deepin.org>
> > ---
> > v1 -> v2: use vma_is_secretmem() instead of directly checking
> >           vma->vm_file->f_op == &secretmem_fops
> > ---
> >  lib/buildid.c | 5 +++++
> >  1 file changed, 5 insertions(+)
> >
> > diff --git a/lib/buildid.c b/lib/buildid.c
> > index 9fc46366597e..34315d09b544 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,10 @@ int build_id_parse(struct vm_area_struct *vma, unsigned char *build_id,
> >       if (!vma->vm_file)
> >               return -EINVAL;
> >
> > +     /* reject secretmem */
>
> Why is this comment different from what is in the original commit?  Same
> for your other backports.  Please try to keep it as identical to the
> original whenever possible as we have to maintain this for a very long
> time.
>
> thanks,
>
> greg k-h
>
>

Original comment is in a function named freader_get_folio(),
but folio related changes has not been backported yet.

thanks,

Chen Linxuan

  reply	other threads:[~2025-03-17  5:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17  1:16 Chen Linxuan
2025-03-17  4:18 ` Greg KH
2025-03-17  5:04   ` Chen Linxuan [this message]
2025-03-17  5:14     ` Greg KH
2025-03-17  5:38       ` 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=CAC1kPDNNBj3Hd6s72mA3qxwxC0B69aE7qhM+Az5msvjPy41N5w@mail.gmail.com \
    --to=chenlinxuan@deepin.org \
    --cc=adobriyan@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=greg@kroah.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=stable@vger.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

all inboxes | Powered by JetHome®