[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251007152036.cfbd572d706c40ed79d75642@linux-foundation.org>
Date: Tue, 7 Oct 2025 15:20:36 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Kairui Song <ryncsn@...il.com>
Cc: linux-mm@...ck.org, Kemeng Shi <shikemeng@...weicloud.com>, Kairui Song
<kasong@...cent.com>, Nhat Pham <nphamcs@...il.com>, Baoquan He
<bhe@...hat.com>, Barry Song <baohua@...nel.org>, Chris Li
<chrisl@...nel.org>, Baolin Wang <baolin.wang@...ux.alibaba.com>, David
Hildenbrand <david@...hat.com>, "Matthew Wilcox (Oracle)"
<willy@...radead.org>, Ying Huang <ying.huang@...ux.alibaba.com>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 0/4] mm, swap: misc cleanup and bugfix
On Tue, 07 Oct 2025 04:02:32 +0800 Kairui Song <ryncsn@...il.com> wrote:
> A few cleanups and a bugfix that are either suitable after the swap
> table phase I or found during code review.
>
> Patch 1 is a bugfix and needs to be included in the stable branch,
> the rest have no behavior change.
fyi, the presentation of the series suggests that [1/4] is not a hotfix
- that it won't hit mainline (and then -stable) until after 6.19-rc1.
Which sounds OK given this:
> So far, no issues have been observed or reported with typical SSD setups
> under months of high pressure. This issue was found during my code
> review. But by hacking the kernel a bit: adding a mdelay(100) in the
> async discard path, this issue will be observable with WARNING triggered
> by the wrong GFP and cond_resched in the bio layer.
Powered by blists - more mailing lists