From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: junho.cha@xcena.com, "Andrew Morton" <akpm@linux-foundation.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
"Jan Kara" <jack@suse.cz>, "Zi Yan" <ziy@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Liam R. Howlett" <liam@infradead.org>,
"Vlastimil Babka" <vbabka@kernel.org>,
"Mike Rapoport" <rppt@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Michal Hocko" <mhocko@suse.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/migrate: drop the fault lock and wait killably for migration entries
Date: Tue, 17 Nov 2026 10:01:10 +0000 [thread overview]
Message-ID: <avwj171O8QMg9Akg@gremlin> (raw)
In-Reply-To: <d463af46-13c3-47f7-8b26-702a8edcd140@kernel.org>
On Tue, Nov 17, 2026 at 10:46:24AM +0100, David Hildenbrand (Arm) wrote:
>
> Hi,
>
> I assume
>
> * this was not hit in the wild but found with an LLM.
> * Most of the code and patch description were written with an LLM.
>
> Correct?
Clearly. Their 2nd patch ever *eye roll*.
The patch itself adds FAR too much complexity, and clearly there is no
understanding.
This code path needs simplifying, and I will be making significant changes to
migration for scaleable CoW anyway. So absolutely no to this patch or any
variant of it.
>
> --
> Cheers,
>
> David
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-11-17 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 9:26 [PATCH] mm/migrate: drop the fault lock and wait killably for migration entries Junho Cha
2026-11-17 9:26 ` Junho Cha via B4 Relay
2026-11-17 9:46 ` David Hildenbrand (Arm)
2026-11-17 10:01 ` Lorenzo Stoakes (ARM) [this message]
2026-11-18 0:36 ` 차준호
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=avwj171O8QMg9Akg@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@kernel.org \
--cc=jack@suse.cz \
--cc=junho.cha@xcena.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=vbabka@kernel.org \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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.