All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: ZhengYuan Huang <gality369@gmail.com>,
	akpm@linux-foundation.org,  Liam.Howlett@oracle.com,
	vbabka@kernel.org, rppt@kernel.org, surenb@google.com,
	 mhocko@suse.com, willy@infradead.org, linux-mm@kvack.org,
	 linux-kernel@vger.kernel.org, baijiaju1990@gmail.com,
	r33s3n6@gmail.com, zzzccc427@gmail.com
Subject: Re: [PATCH] mm: prepare anon_vma before swapin rmap
Date: Sat, 18 Apr 2026 10:35:36 +0100	[thread overview]
Message-ID: <aeNP7mtx878gynXS@lucifer> (raw)
In-Reply-To: <fb80d953-93de-4ce3-80c6-15cd53dd956f@kernel.org>

On Fri, Apr 17, 2026 at 01:57:59PM +0200, David Hildenbrand (Arm) wrote:
> Maybe there was a scenario where we could have lost vma->anon_vma during
> a merge, resulting in a swapped page in an anon_vma.

Unless there's a bug (and correct me if I'm misinterpreting), VMA merge requires
vma->anon_vma to either be equal for merged adjacent VMAs, or one or the other
VMA to have NULL vma->anon_vma, in which case we set vma->anon_vma in the merged
VMA.

Thanks, Lorenzo


  parent reply	other threads:[~2026-04-18  9:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  1:16 [PATCH] mm: prepare anon_vma before swapin rmap ZhengYuan Huang
2026-04-17  4:03 ` Matthew Wilcox
2026-04-18  9:38   ` Lorenzo Stoakes
2026-04-17 10:53 ` David Hildenbrand (Arm)
2026-04-17 11:57   ` David Hildenbrand (Arm)
2026-04-17 13:03     ` Matthew Wilcox
2026-04-17 13:36       ` Vlastimil Babka (SUSE)
2026-04-17 15:09         ` Matthew Wilcox
2026-04-18  9:35     ` Lorenzo Stoakes [this message]
2026-04-19  8:19       ` David Hildenbrand (Arm)
2026-04-19 14:21         ` Lorenzo Stoakes
2026-04-22  7:59           ` ZhengYuan Huang
2026-04-22 10:20             ` Lorenzo Stoakes

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=aeNP7mtx878gynXS@lucifer \
    --to=ljs@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=baijiaju1990@gmail.com \
    --cc=david@kernel.org \
    --cc=gality369@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=r33s3n6@gmail.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=willy@infradead.org \
    --cc=zzzccc427@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.