linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Xu <jeffxu@chromium.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
	akpm@linux-foundation.org,  keescook@chromium.org,
	jannh@google.com, torvalds@linux-foundation.org,
	 adhemerval.zanella@linaro.org, linux-kernel@vger.kernel.org,
	 linux-hardening@vger.kernel.org, linux-mm@kvack.org,
	jorgelo@chromium.org,  sroettger@google.com, ojeda@kernel.org,
	adobriyan@gmail.com,  anna-maria@linutronix.de,
	mark.rutland@arm.com, linus.walleij@linaro.org,  Jason@zx2c4.com,
	deller@gmx.de, rdunlap@infradead.org, davem@davemloft.net,
	 hch@lst.de, peterx@redhat.com, hca@linux.ibm.com,
	f.fainelli@gmail.com,  gerg@kernel.org,
	dave.hansen@linux.intel.com, mingo@kernel.org,  ardb@kernel.org,
	mhocko@suse.com, 42.hyeyoo@gmail.com, peterz@infradead.org,
	 ardb@google.com, enh@google.com, rientjes@google.com,
	groeck@chromium.org,  lorenzo.stoakes@oracle.com
Subject: Re: [RFC PATCH v2 1/1] exec: seal system mappings
Date: Thu, 17 Oct 2024 09:12:00 -0700	[thread overview]
Message-ID: <CABi2SkVAXhqb+r5HzD5fWnHs1g2tjg8CShXX0+xnagqeVXrttA@mail.gmail.com> (raw)
In-Reply-To: <20241017083752.GA15167@redhat.com>

On Thu, Oct 17, 2024 at 1:38 AM Oleg Nesterov <oleg@redhat.com> wrote:
>
> On 10/16, Jeff Xu wrote:
> >
> > On Wed, Oct 16, 2024 at 6:10 PM Liam R. Howlett <Liam.Howlett@oracle.com> wrote:
> > >
> > > > +     exec.seal_system_mappings = [KNL]
> > > > +                     Format: { never | always }
> > > > +                     Seal system mappings: vdso, vvar, sigpage, uprobes,
> > > > +                     vsyscall.
> > > > +                     This overwrites KCONFIG CONFIG_SEAL_SYSTEM_MAPPINGS_*
> > > > +                     - 'never':  never seal system mappings.
> > >
> > > Not true, uprobes are sealed when 'never' is selected.
> > >
> > Thanks. I forgot to uprobes from the description in Kconfig and
> > kernel-parameters.txt, will update.
>
> Jeff, I am sorry for confusion.
>
> No need to make uprobes "special" and complicate the logic/documentation.
>
> I just meant that, unlike vdso, it is always safe/good to mseal the "[uprobes]"
> vma, regardless of config/boot options.
>
> Please do what you think is right, I am fine either way.
>
OK, in that case, V1 is a better approach, using the same config to
control all system mappings.
I will send V1 to revert that.

Thanks for clarifying.
-Jeff

> Oleg.
>


  reply	other threads:[~2024-10-17 16:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 21:50 [RFC PATCH v2 0/1] " jeffxu
2024-10-14 21:50 ` [RFC PATCH v2 1/1] exec: " jeffxu
2024-10-16 21:26   ` Kees Cook
2024-10-16 22:06     ` Jeff Xu
2024-10-17  3:56       ` Jeff Xu
2024-10-17  1:10   ` Liam R. Howlett
2024-10-17  3:43     ` Jeff Xu
2024-10-17  8:37       ` Oleg Nesterov
2024-10-17 16:12         ` Jeff Xu [this message]
2024-10-17 16:01       ` Liam R. Howlett
2024-11-11 19:10         ` Jeff Xu
2024-11-11 22:35           ` Liam R. Howlett
2024-11-13 21:38             ` Jeff Xu
2024-10-16 23:18 ` [RFC PATCH v2 0/1] " Liam R. Howlett
2024-10-17  0:58   ` Jeff Xu
2024-10-17  2:03     ` Liam R. Howlett
2024-11-11 18:25       ` Jeff Xu

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=CABi2SkVAXhqb+r5HzD5fWnHs1g2tjg8CShXX0+xnagqeVXrttA@mail.gmail.com \
    --to=jeffxu@chromium.org \
    --cc=42.hyeyoo@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=anna-maria@linutronix.de \
    --cc=ardb@google.com \
    --cc=ardb@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=deller@gmx.de \
    --cc=enh@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=gerg@kernel.org \
    --cc=groeck@chromium.org \
    --cc=hca@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=jannh@google.com \
    --cc=jorgelo@chromium.org \
    --cc=keescook@chromium.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mark.rutland@arm.com \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterx@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=rientjes@google.com \
    --cc=sroettger@google.com \
    --cc=torvalds@linux-foundation.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