Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "李佑鸿 " <dayou5941@163.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: akpm@linux-foundation.org, david@kernel.org, ziy@nvidia.com,
	linux-mm@kvack.org, "Li Youhong" <liyouhong@kylinos.cn>,
	"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>
Subject: Re:Re: [PATCH] mm/huge_memory: add VM_WARN_ON_ONCE_FOLIO() in min_order_for_split()
Date: Thu, 6 Aug 2026 15:34:43 +0800 (CST)	[thread overview]
Message-ID: <17316ab0.5714.19fd5fef275.Coremail.dayou5941@163.com> (raw)
In-Reply-To: <anQqEfCEbWmm5vX8@lucifer>


















At 2026-08-06 14:32:41, "Lorenzo Stoakes (ARM)" <ljs@kernel.org> wrote:
>Sigh. NAK.
>
>This will trigger immediately.
>
>You're sending this separate from the fix that makes this make any sense,
>and I literally told you to send it as a single patch.
>
>Please do what maintainers tell you to do.
>
>I'm pretty convinced you're just doing unacknowledged AI slopping here
>because you don't seem to have any understanding of the basics.
>
>Again inclined to just do the patch myself on that basis...!

>



Hi Lorenzo,
Thank you for your feedback, and I apologize for that.
You are right — I may have misunderstood what you meant by "separate patch." I thought you wanted it sent as an independent patch, but you clearly meant as part of the same series, placed after the fix patch that makes the warning meaningful.
I'll resend the full series as a single patchset (v5 1/2 + 2/2):

Patch 1: mm/memory-failure: fix folio refcount leak and locking in
soft/hard offline
Patch 2: mm/huge_memory: add VM_WARN_ON_ONCE_FOLIO() in
min_order_for_split()

The second patch depends on the first, so they must go together as
you originally requested.
I'll send this out by tomorrow as you asked. My apologies for the
noise and the wasted review time.

Thanks,
Youhong

>On Thu, Aug 06, 2026 at 11:21:16AM +0800, dayou5941@163.com wrote:
>> From: Li Youhong <liyouhong@kylinos.cn>
>>
>> min_order_for_split() expects to be called with the folio locked,
>> but does not enforce this itself. Add a VM_WARN_ON_ONCE_FOLIO()
>> check to validate this assumption and document the locking requirement.
>>
>> Suggested-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>> Signed-off-by: Li Youhong <liyouhong@kylinos.cn>
>> ---
>>  mm/huge_memory.c | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>> index 58cabe6af33d..e3f16dadc1d4 100644
>> --- a/mm/huge_memory.c
>> +++ b/mm/huge_memory.c
>> @@ -4300,6 +4300,8 @@ int folio_split(struct folio *folio, unsigned int new_order,
>>   */
>>  unsigned int min_order_for_split(struct folio *folio)
>>  {
>> +	VM_WARN_ON_ONCE_FOLIO(!folio_test_locked(folio), folio);
>> +
>>  	if (folio_test_anon(folio))
>>  		return 0;
>>
>> --
>> 2.25.1
>>
>
>--
>Cheers, Lorenzo

  reply	other threads:[~2026-08-06  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  3:21 [PATCH] mm/huge_memory: add VM_WARN_ON_ONCE_FOLIO() in min_order_for_split() dayou5941
2026-08-06  6:32 ` Lorenzo Stoakes (ARM)
2026-08-06  7:34   ` 李佑鸿  [this message]
2026-08-06  7:36     ` Lorenzo Stoakes (ARM)
2026-08-06 11:15       ` David Hildenbrand (Arm)

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=17316ab0.5714.19fd5fef275.Coremail.dayou5941@163.com \
    --to=dayou5941@163.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liyouhong@kylinos.cn \
    --cc=ljs@kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox