From: Wei Yang <richard.weiyang@gmail.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, vbabka@suse.cz,
lorenzo.stoakes@oracle.com, linux-mm@kvack.org,
Jann Horn <jannh@google.com>,
stable@vger.kernel.org
Subject: Re: [PATCH hotfix 6.12 v2] mm/mlock: set the correct prev on failure
Date: Tue, 29 Oct 2024 01:24:03 +0000 [thread overview]
Message-ID: <20241029012403.5h7sajuj5rxtoyn5@master> (raw)
In-Reply-To: <z54jwszrhsjewssvswsmucnbjgzyzygvzlmnkiniwxct6akcfw@nwc2kwht2ofq>
On Mon, Oct 28, 2024 at 11:00:43AM -0400, Liam R. Howlett wrote:
>* Wei Yang <richard.weiyang@gmail.com> [241027 08:34]:
>> 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.
>>
>> 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.
>>
>> [lorenzo: provide a better fix and rephrase the log]
>>
>> Fixes: 94d7d9233951 ("mm: abstract the vma_merge()/split_vma() pattern for mprotect() et al.")
>>
>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>> CC: Liam R. Howlett <Liam.Howlett@Oracle.com>
>> CC: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>> CC: Vlastimil Babka <vbabka@suse.cz>
>> CC: Jann Horn <jannh@google.com>
>> Cc: <stable@vger.kernel.org>
>>
>> ---
>> v2:
>> rearrange the fix and change log per Lorenzo's suggestion
>> add fix tag and cc stable
>>
>> ---
>> mm/mlock.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/mm/mlock.c b/mm/mlock.c
>> index e3e3dc2b2956..cde076fa7d5e 100644
>> --- a/mm/mlock.c
>> +++ b/mm/mlock.c
>> @@ -725,14 +725,17 @@ static int apply_mlockall_flags(int flags)
>> }
>>
>> for_each_vma(vmi, vma) {
>> + int error;
>> vm_flags_t newflags;
>>
>> newflags = vma->vm_flags & ~VM_LOCKED_MASK;
>> newflags |= to_add;
>>
>> - /* Ignore errors */
>> - mlock_fixup(&vmi, vma, &prev, vma->vm_start, vma->vm_end,
>> - newflags);
>> + error = mlock_fixup(&vmi, vma, &prev, vma->vm_start, vma->vm_end,
>> + newflags);
>> + /* Ignore errors, but prev needs fixing up. */
>> + if (error)
>> + prev = vma;
>
>I don't think we need a local variable for the error since it's not used
>for anything besides ensuring there was a non-zero return here, but it
>probably doesn't make a difference. I'd have to check the assembly to
>be sure.
>
>Either way,
>
>Reviewed-by: Liam R. Howlett <Liam.Howlett@Oracle.com>
>
Thanks
>> cond_resched();
>> }
>> out:
>> --
>> 2.34.1
>>
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2024-10-29 1:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 12:33 Wei Yang
2024-10-27 13:32 ` Lorenzo Stoakes
2024-10-28 0:53 ` Andrew Morton
2024-10-28 2:47 ` Wei Yang
2024-10-28 15:00 ` Liam R. Howlett
2024-10-29 1:24 ` Wei Yang [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=20241029012403.5h7sajuj5rxtoyn5@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=stable@vger.kernel.org \
--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