Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Fujunjie <fujunjie1@qq.com>
To: Lorenzo Stoakes <ljs@kernel.org>, Jann Horn <jannh@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@kernel.org>,
	Shuah Khan <shuah@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] mm/mremap: unmap full fixed target for multi-VMA moves
Date: Tue, 12 May 2026 15:24:24 +0800	[thread overview]
Message-ID: <tencent_B49EC91555E7B93CE646566E0A2DBEB9BE09@qq.com> (raw)
In-Reply-To: <agICeiIEshWf-1xa@lucifer>



On 5/12/2026 12:30 AM, Lorenzo Stoakes wrote:
> Yeah let's go with that then I think :)


Thanks Lorenzo and Jann.

I agree that the patch as posted goes in the wrong direction by treating
source gaps as ranges that should be propagated to the destination.  Please
drop this patch.

If disallowing source gaps in this multi-VMA move path still sounds right,
I can look into a v2/new patch that rejects sparse source ranges up front
instead.

Thanks,
fujunjie



  reply	other threads:[~2026-05-12  7:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 18:24 [PATCH] mm/mremap: unmap full fixed target for multi-VMA moves fujunjie
2026-05-11 15:05 ` Lorenzo Stoakes
2026-05-11 15:19   ` Jann Horn
2026-05-11 15:32     ` Lorenzo Stoakes
2026-05-11 15:40       ` Jann Horn
2026-05-11 16:00         ` Lorenzo Stoakes
2026-05-11 16:02           ` Jann Horn
2026-05-11 16:30             ` Lorenzo Stoakes
2026-05-12  7:24               ` Fujunjie [this message]
2026-05-12 13:59                 ` 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=tencent_B49EC91555E7B93CE646566E0A2DBEB9BE09@qq.com \
    --to=fujunjie1@qq.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=shuah@kernel.org \
    --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