public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: kartikey406@gmail.com, usama.arif@linux.dev,
	Liam.Howlett@oracle.com, ziy@nvidia.com,
	syzbot+a7067a757858ac8eb085@syzkaller.appspotmail.com,
	akpm@linux-foundation.org, baohua@kernel.org,
	baolin.wang@linux.alibaba.com, dev.jain@arm.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org,
	npache@redhat.com, ryan.roberts@arm.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in deferred_split_folio
Date: Wed, 1 Apr 2026 19:54:14 +0800	[thread overview]
Message-ID: <87a48c70-b6fd-48f6-9ec0-7eb2dc6cc3d1@linux.dev> (raw)
In-Reply-To: <c5d01704-9035-482a-b562-ef5a0c163d4d@linux.dev>



On 2026/4/1 19:51, Lance Yang wrote:
> 
> 
> On 2026/4/1 19:44, David Hildenbrand (Arm) wrote:
>> On 4/1/26 13:41, Lance Yang wrote:
>>>
>>>
>>> On 2026/4/1 19:38, David Hildenbrand (Arm) wrote:
>>>> On 4/1/26 13:34, Lance Yang wrote:
>>>>>
>>>>>
>>>>> ACK.
>>>>>
>>>>>
>>>>> certainly, will do! But commit[1] ("mm: migrate: requeue destination
>>>>> folio on deferred split queue") is only in mm-stable now, not yet
>>>>> upstream/stable ...
>>>>
>>>> It's tricky. The original commit will be backported to stable kernels,
>>>> so we want also the fix to be backported to the same stable kernels.
>>>>
>>>> The commit id in mm-stable is "stable" now.
>>>
>>> Emm... Not a big deal, I guess. We can always submit a stable backport
>>> once that fix gets merged into stable :D
>>
>> What's the problem with tagging the commit right way as Cc: stable?
> 
> Sure, that makes sense. I'll add "Cc: stable" to the fix as well, so
> it can follow 8a8ca142a488 into stable ;)

8a8ca142a488 refers to commit "mm: migrate: requeue destination folio on 
deferred split queue".


      reply	other threads:[~2026-04-01 11:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EE70ZGRNE12@zendesk.com>
2026-04-01  6:08 ` [syzbot] [mm?] WARNING in deferred_split_folio syzbot
2026-04-01  6:09   ` Request received Yail
2026-04-01  8:10   ` [syzbot] [mm?] WARNING in deferred_split_folio Lance Yang
2026-04-01  8:59     ` Lance Yang
2026-04-01  9:36       ` David Hildenbrand (Arm)
2026-04-01 10:16       ` David Hildenbrand (Arm)
2026-04-01 10:53         ` Lance Yang
2026-04-01 11:00           ` David Hildenbrand (Arm)
2026-04-01 11:20             ` Lance Yang
2026-04-01 11:22               ` David Hildenbrand (Arm)
2026-04-01 11:34                 ` Lance Yang
2026-04-01 11:38                   ` David Hildenbrand (Arm)
2026-04-01 11:41                     ` Lance Yang
2026-04-01 11:44                       ` David Hildenbrand (Arm)
2026-04-01 11:51                         ` Lance Yang
2026-04-01 11:54                           ` Lance Yang [this message]

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=87a48c70-b6fd-48f6-9ec0-7eb2dc6cc3d1@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=kartikey406@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=npache@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=syzbot+a7067a757858ac8eb085@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=usama.arif@linux.dev \
    --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