From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@kernel.org>,
Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>,
Jeff Xu <jeffxu@chromium.org>,
David Hildenbrand <david@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
antonius <bluedragonsec2023@gmail.com>
Subject: Re: [PATCH mm-hotfixes] mm/mseal: update VMA end correctly on merge
Date: Fri, 27 Mar 2026 15:52:02 +0000 [thread overview]
Message-ID: <d6348e8e-b9ba-4404-848e-8db941ffdfbe@lucifer.local> (raw)
In-Reply-To: <20260327082446.4e7fd5398043d56cebb35a54@linux-foundation.org>
On Fri, Mar 27, 2026 at 08:24:46AM -0700, Andrew Morton wrote:
> On Fri, 27 Mar 2026 09:06:40 +0000 "Lorenzo Stoakes (Oracle)" <ljs@kernel.org> wrote:
>
> > --- a/mm/mseal.c
> > +++ b/mm/mseal.c
> > @@ -66,7 +66,7 @@ static int mseal_apply(struct mm_struct *mm,
> > prev = vma;
> >
> > for_each_vma_range(vmi, vma, end) {
> > - const unsigned long curr_end = MIN(vma->vm_end, end);
> > + unsigned long curr_end = MIN(vma->vm_end, end);
> >
> > if (!(vma->vm_flags & VM_SEALED)) {
> > vm_flags_t vm_flags = vma->vm_flags | VM_SEALED;
> > @@ -76,6 +76,7 @@ static int mseal_apply(struct mm_struct *mm,
> > if (IS_ERR(vma))
> > return PTR_ERR(vma);
> > vm_flags_set(vma, VM_SEALED);
> > + curr_end = vma->vm_end; /* Merge may have updated. */
> > }
> >
> > prev = vma;
>
> This led to some rework in your "mm/vma: convert
> vma_modify_flags[_uffd]() to use vma_flags_t". Please check my
> handiwork.
>
> reject:
>
> --- mm/mseal.c~mm-vma-convert-vma_modify_flags-to-use-vma_flags_t
> +++ mm/mseal.c
> @@ -68,14 +68,17 @@ static int mseal_apply(struct mm_struct
> for_each_vma_range(vmi, vma, end) {
> const unsigned long curr_end = MIN(vma->vm_end, end);
>
> - if (!(vma->vm_flags & VM_SEALED)) {
> - vm_flags_t vm_flags = vma->vm_flags | VM_SEALED;
> + if (!vma_test(vma, VMA_SEALED_BIT)) {
> + vma_flags_t vma_flags = vma->flags;
> +
> + vma_flags_set(&vma_flags, VMA_SEALED_BIT);
>
> vma = vma_modify_flags(&vmi, prev, vma, curr_start,
> - curr_end, &vm_flags);
> + curr_end, &vma_flags);
> if (IS_ERR(vma))
> return PTR_ERR(vma);
> - vm_flags_set(vma, VM_SEALED);
> + vma_start_write(vma);
> + vma_set_flags(vma, VMA_SEALED_BIT);
> }
>
> prev = vma;
>
> resolution:
>
> static int mseal_apply(struct mm_struct *mm,
> unsigned long start, unsigned long end)
> {
> struct vm_area_struct *vma, *prev;
> unsigned long curr_start = start;
> VMA_ITERATOR(vmi, mm, start);
>
> /* We know there are no gaps so this will be non-NULL. */
> vma = vma_iter_load(&vmi);
> prev = vma_prev(&vmi);
> if (start > vma->vm_start)
> prev = vma;
>
> for_each_vma_range(vmi, vma, end) {
> unsigned long curr_end = MIN(vma->vm_end, end);
>
> if (!vma_test(vma, VMA_SEALED_BIT)) {
> vma_flags_t vma_flags = vma->flags;
>
> vma_flags_set(&vma_flags, VMA_SEALED_BIT);
>
> vma = vma_modify_flags(&vmi, prev, vma, curr_start,
> curr_end, &vma_flags);
> if (IS_ERR(vma))
> return PTR_ERR(vma);
> vma_start_write(vma);
> vma_set_flags(vma, VMA_SEALED_BIT);
> curr_end = vma->vm_end; /* Merge may have updated. */
> }
>
> prev = vma;
> curr_start = curr_end;
> }
>
> return 0;
> }
>
Thanks that looks correct!
Cheers, Lorenzo
next prev parent reply other threads:[~2026-03-27 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 9:06 Lorenzo Stoakes (Oracle)
2026-03-27 9:15 ` Pedro Falcato
2026-03-27 9:16 ` Lorenzo Stoakes (Oracle)
2026-03-27 13:22 ` Vlastimil Babka (SUSE)
2026-03-27 15:24 ` Andrew Morton
2026-03-27 15:52 ` Lorenzo Stoakes (Oracle) [this message]
2026-03-27 16:57 ` David Hildenbrand (Arm)
2026-03-27 17:23 ` Lorenzo Stoakes (Oracle)
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=d6348e8e-b9ba-4404-848e-8db941ffdfbe@lucifer.local \
--to=ljs@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bluedragonsec2023@gmail.com \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=jeffxu@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pfalcato@suse.de \
--cc=vbabka@kernel.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