All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: Fujunjie <fujunjie1@qq.com>
Cc: Jann Horn <jannh@google.com>,
	 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 14:59:49 +0100	[thread overview]
Message-ID: <agMyDHx5MxR0igFY@lucifer> (raw)
In-Reply-To: <tencent_B49EC91555E7B93CE646566E0A2DBEB9BE09@qq.com>

On Tue, May 12, 2026 at 03:24:24PM +0800, Fujunjie wrote:
>
>
> 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.

Sorry I really want to think about this a little more + make sure the
semantics are sane, so I'd rather take a look at this myself.

I do really hate to take something away from newer contributors but in this
case things are quite fiddly so I want to make sure everything's correct :)

>
> Thanks,
> fujunjie
>

Thanks, Lorenzo

  reply	other threads:[~2026-05-12 13:59 UTC|newest]

Thread overview: 11+ 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
2026-05-12 13:59                 ` Lorenzo Stoakes [this message]
2026-05-13 11:49                   ` Fujunjie

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=agMyDHx5MxR0igFY@lucifer \
    --to=ljs@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=fujunjie1@qq.com \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.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 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.