[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aBNrEbVkpLHkK7eF@casper.infradead.org>
Date: Thu, 1 May 2025 13:37:37 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Shivank Garg <shivankg@....com>, shaggy@...nel.org, david@...hat.com,
wangkefeng.wang@...wei.com, jane.chu@...cle.com, ziy@...dia.com,
donettom@...ux.ibm.com, apopple@...dia.com,
jfs-discussion@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
linux-mm@...ck.org,
syzbot+8bb6fd945af4e0ad9299@...kaller.appspotmail.com
Subject: Re: [PATCH V5 0/2] JFS: Implement migrate_folio for
jfs_metapage_aops
On Wed, Apr 30, 2025 at 02:21:35PM -0700, Andrew Morton wrote:
> On Wed, 30 Apr 2025 10:01:49 +0000 Shivank Garg <shivankg@....com> wrote:
> > This patch addresses a warning that occurs during memory compaction due
> > to JFS's missing migrate_folio operation. The warning was introduced by
> > commit 7ee3647243e5 ("migrate: Remove call to ->writepage") which added
> > explicit warnings when filesystem don't implement migrate_folio.
>
> Do we think these patches should be backported into -stable kernels?
>
> Or maybe we should simply remove the warning from -stable kernels then
> re-add it when we're confident that all in-tree filesystems are good?
7ee3647243e5 is not yet in Linus' tree, let alone in -stable.
Powered by blists - more mailing lists