Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Yeoreum Yun <yeoreum.yun@arm.com>
Cc: linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	 linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	david@kernel.org, liam@infradead.org,  vbabka@kernel.org,
	rppt@kernel.org, surenb@google.com, mhocko@suse.com
Subject: Re: [PATCH] kselftest: mm: fix potential failure for merged VMA in guard-regions
Date: Fri, 11 Sep 2026 14:51:09 +0100	[thread overview]
Message-ID: <aqQG5LgqXnrmY1_l@gremlin> (raw)
In-Reply-To: <aqQDbfMOVasuejA3@e129823.arm.com>

On Fri, Sep 11, 2026 at 02:34:37PM +0100, Yeoreum Yun wrote:
> On Fri, Sep 11, 2026 at 01:59:31PM +0100, Lorenzo Stoakes (ARM) wrote:
> > On Fri, Sep 11, 2026 at 01:35:34PM +0100, Yeoreum Yun wrote:
> > > check_vmflag_guard() uses /proc/self/smaps to retrieve the VMA flags,
> > > but this can fail if the mapping is merged with an adjacent VMA.
> > >
> > > To avoid this potential failure, first allocate a temporary region with
> > > extra pages at both ends, unmap it, and then map the test region within
> > > the temporary address range, leaving an unmapped page on each side to
> > > prevent VMA merging.
> > >
> > > Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
> > > ---
> > >  tools/testing/selftests/mm/guard-regions.c | 14 ++++++++++++--
> > >  1 file changed, 12 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/tools/testing/selftests/mm/guard-regions.c b/tools/testing/selftests/mm/guard-regions.c
> > > index 5c8ec3ca75d7..a28a57d34e97 100644
> > > --- a/tools/testing/selftests/mm/guard-regions.c
> > > +++ b/tools/testing/selftests/mm/guard-regions.c
> > > @@ -2257,8 +2257,18 @@ TEST_F(guard_regions, smaps)
> > >  	char *ptr, *ptr2;
> > >  	int i;
> > >
> > > -	/* Map a region. */
> > > -	ptr = mmap_(self, variant, NULL, 10 * page_size, PROT_READ | PROT_WRITE, 0, 0);
> > > +	/* Try to Map a region. */
> >
> > Map -> map
> >
> > > +	ptr = mmap_(self, variant, NULL, 12 * page_size, PROT_READ | PROT_WRITE, 0, 0);
> >
> > Should be PROT_NONE otherwise it'll merge with the below.
>
> It doesn't matter. since this memory is unmapped and then second map
> at ptr + page_size.
>
> IOW, though the first one is merged, it unammped and then
> the second is allocated at ptr + page_size, it wouldn't be merged:
>
>   after unmap:
>    [existing VMA][ 12 pages ][existing VMA]
>
>   second:
>    [exiting VMA] [hole (page)] [ 10 pages (for test)] [hole (page)] [existing VMA]
>
> Am I missing something?

Yeah, unmapped (unfaulted) VMAs can be merged with mapped (faulted) VMAs.

In general it's also better to be explicit by specifying distinct attributes
anyway to spell out clearly that the VMAs are intended to perform that task.

>
> --
> Sincerely,
> Yeoreum Yun

--
Cheers, Lorenzo


  reply	other threads:[~2026-09-11 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 12:35 [PATCH] kselftest: mm: fix potential failure for merged VMA in guard-regions Yeoreum Yun
2026-09-11 12:59 ` Lorenzo Stoakes (ARM)
2026-09-11 13:34   ` Yeoreum Yun
2026-09-11 13:51     ` Lorenzo Stoakes (ARM) [this message]
2026-09-11 14:14       ` Lorenzo Stoakes (ARM)
2026-09-11 14:18         ` Yeoreum Yun

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=aqQG5LgqXnrmY1_l@gremlin \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=yeoreum.yun@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox