From: Oleg Nesterov <oleg@redhat.com>
To: Jeff Xu <jeffxu@chromium.org>
Cc: Kees Cook <keescook@chromium.org>,
srikar@linux.vnet.ibm.com, Ryan Roberts <ryan.roberts@arm.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"glider@google.com" <glider@google.com>,
Matthew Wilcox <willy@infradead.org>,
zokeefe@google.com, hughd@google.com, luto@amacapital.net,
"jmarchan@redhat.com" <jmarchan@redhat.com>,
"rientjes@google.com" <rientjes@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: question on [uprobes] special vma
Date: Sat, 3 Aug 2024 00:21:46 +0200 [thread overview]
Message-ID: <20240802222145.GC20135@redhat.com> (raw)
In-Reply-To: <CABi2SkXqkC3wX4wnhXTXrLSs-6PLO-Fj4g=Hcvqq=ppv4QWUzA@mail.gmail.com>
On 08/02, Jeff Xu wrote:
>
> > So it seems that xol_add_vma() can just pass the additional VM_SEALED
> > flag to _install_special_mapping(), no?
> >
> Yes. Before I make that change, I want to confirm that [uprobes] VMA
> is immutable during the lifetime of the process, hence this email.
OK, thanks,
> > But why it depends on CONFIG_64_BIT?
> >
> It needn't, but the vm_flags_t in the vma struct for 32 bit is full,
Ah, indeed ;)
Thanks!
Oleg.
prev parent reply other threads:[~2024-08-02 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 23:38 question on [uprobes] special vma Jeff Xu
2024-08-02 9:00 ` Oleg Nesterov
2024-08-02 14:59 ` Jeff Xu
2024-08-02 22:21 ` Oleg Nesterov [this message]
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=20240802222145.GC20135@redhat.com \
--to=oleg@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=glider@google.com \
--cc=hughd@google.com \
--cc=jeffxu@chromium.org \
--cc=jmarchan@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=rientjes@google.com \
--cc=ryan.roberts@arm.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=zokeefe@google.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.