linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Vlastimil Babka <vbabka@suse.cz>,
	Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH] mm/madvise: process_madvise() drop capability check if same mm
Date: Fri, 13 Sep 2024 10:35:58 -0400	[thread overview]
Message-ID: <x4lutkd66z46qeymya5r5k4y6luggvsx3phoyt2gohzq6txe4f@cut73peawi2d> (raw)
In-Reply-To: <k4euomzfssryq7r3tglsvk372d4vj3nd52ge6hjmgoozvjubww@jvqup75daqsv>


..Add Shakeel's new email address

* Liam R. Howlett <Liam.Howlett@oracle.com> [240913 10:31]:
> * Lorenzo Stoakes <lorenzo.stoakes@oracle.com> [240913 10:06]:
> > In commit 96cfe2c0fd23 ("mm/madvise: replace ptrace attach requirement for
> > process_madvise") process_madvise() was updated to require the caller to
> > possess the CAP_SYS_NICE capability to perform the operation, in addition
> > to a check against PTRACE_MODE_READ performed by mm_access().
> > 
> > The mm_access() function explicitly checks to see if the address space of
> > the process being referenced is the current one, in which case no check is
> > performed.
> > 
> > We, however, do not do this when checking the CAP_SYS_NICE capability. This
> > means that we insist on the caller possessing this capability in order to
> > perform madvise() operations on its own address space, which seems
> > nonsensical.
> > 
> > Simply add a check to allow for an invocation of this function with pidfd
> > set to the current process without elevation.
> > 
> > Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> 
> Probably needs a fixes 96cfe2c0fd23 tag?
> 
> Reviewed-by: Liam R. Howlett <Liam.Howlett@Oracle.com>
> 
> > ---
> >  mm/madvise.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/mm/madvise.c b/mm/madvise.c
> > index 4e64770be16c..ff139e57cca2 100644
> > --- a/mm/madvise.c
> > +++ b/mm/madvise.c
> > @@ -1520,7 +1520,7 @@ SYSCALL_DEFINE5(process_madvise, int, pidfd, const struct iovec __user *, vec,
> >  	 * Require CAP_SYS_NICE for influencing process performance. Note that
> >  	 * only non-destructive hints are currently supported.
> >  	 */
> > -	if (!capable(CAP_SYS_NICE)) {
> > +	if (mm != current->mm && !capable(CAP_SYS_NICE)) {
> >  		ret = -EPERM;
> >  		goto release_mm;
> >  	}
> > -- 
> > 2.46.0
> > 


  reply	other threads:[~2024-09-13 14:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 14:06 Lorenzo Stoakes
2024-09-13 14:31 ` Liam R. Howlett
2024-09-13 14:35   ` Liam R. Howlett [this message]
2024-09-13 14:51 ` Vlastimil Babka
2024-09-13 15:56 ` Shakeel Butt
2024-09-15  7:50 ` David Rientjes

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=x4lutkd66z46qeymya5r5k4y6luggvsx3phoyt2gohzq6txe4f@cut73peawi2d \
    --to=liam.howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    /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