From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] mm/mlock: set the correct prev on failure
Date: Mon, 28 Oct 2024 11:07:16 -0400 [thread overview]
Message-ID: <gr6qzjigq6mszyfumlfezsfjuhwea3y3kdoz4hophv7jazyis4@ox6qrsfes2y4> (raw)
In-Reply-To: <ded7692c-dcce-450a-8c76-ae2138aa6d08@lucifer.local>
* Lorenzo Stoakes <lorenzo.stoakes@oracle.com> [241027 07:43]:
> + Vlastimil, Liam, Jann as this is VMA-related.
>
> We really need to bring all VMA-ish files under the VMA MAINTAINERS
> block... will maybe address that once things around that file... calm down
> a bit.
>
> But please cc all of us on anything that even vaguely relates to VMAs,
> thanks!
>
> On Sun, Oct 27, 2024 at 02:56:29AM +0000, Wei Yang wrote:
> > After commit 94d7d9233951 ("mm: abstract the vma_merge()/split_vma()
> > pattern for mprotect() et al."), if vma_modify_flags() return error, the
> > vma is set to an error code. This will lead to an invalid prev be
> > returned.
>
> This is a great spot, but this commit message is missing critical
> details. This is only meaningful for apply_mlockall_flags() which is both
> ignoring errors AND assuming mlock_fixup(), even on error, is correctly
> updating the prev state. Which is imo wrong.
>
> So I'd _add_ a bit more information here like:
>
> Generally this shouldn't matter as the caller should treat an error as
> indicating state is now invalidated, however unfortunately
> apply_mlockall_flags() does not check for errors and assumes that
> mlock_fixup() correctly maintains prev even if an error were to occur.
>
> This patch fixes that assumption.
>
> We'll also need to backport this, so a:
>
> Fixes: 94d7d9233951 ("mm: abstract the vma_merge()/split_vma() pattern for mprotect() et al.")
> Cc: <stable@vger.kernel.org>
>
> Needs to be added, and make the next revision [PATCH hotfix 6.12 v2] to
> make it clear this needs to go to 6.12.
>
> >
> > Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> > CC: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > ---
> > mm/mlock.c | 7 ++++---
> > 1 file changed, 4 insertions(+), 3 deletions(-)
> >
> > diff --git a/mm/mlock.c b/mm/mlock.c
> > index e3e3dc2b2956..8c3f9cf8f960 100644
> > --- a/mm/mlock.c
> > +++ b/mm/mlock.c
> > @@ -478,11 +478,12 @@ static int mlock_fixup(struct vma_iterator *vmi, struct vm_area_struct *vma,
> > /* don't set VM_LOCKED or VM_LOCKONFAULT and don't count */
> > goto out;
> >
> > - vma = vma_modify_flags(vmi, *prev, vma, start, end, newflags);
> > - if (IS_ERR(vma)) {
> > - ret = PTR_ERR(vma);
> > + *prev = vma_modify_flags(vmi, *prev, vma, start, end, newflags);
> > + if (IS_ERR(*prev)) {
> > + ret = PTR_ERR(*prev);
> > goto out;
> > }
> > + vma = *prev;
If we move the assignment *prev = vma to the start of this function,
then we can just get rid of the "out:" label and return on errors.
But the v2 seems fine,
Liam
next prev parent reply other threads:[~2024-10-28 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 2:56 Wei Yang
2024-10-27 11:41 ` Lorenzo Stoakes
2024-10-27 12:15 ` Wei Yang
2024-10-27 12:38 ` Wei Yang
2024-10-28 15:07 ` Liam R. Howlett [this message]
2024-10-29 1:23 ` Wei Yang
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=gr6qzjigq6mszyfumlfezsfjuhwea3y3kdoz4hophv7jazyis4@ox6qrsfes2y4 \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=richard.weiyang@gmail.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