[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250415232501.iypezdhizhttidpc@offworld>
Date: Tue, 15 Apr 2025 19:02:07 -0700
From: Davidlohr Bueso <dave@...olabs.net>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: Jan Kara <jack@...e.cz>, Christian Brauner <brauner@...nel.org>,
tytso@....edu, adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org,
riel@...riel.com, willy@...radead.org, hannes@...xchg.org,
oliver.sang@...el.com, david@...hat.com, axboe@...nel.dk,
hare@...e.de, david@...morbit.com, djwong@...nel.org,
ritesh.list@...il.com, linux-fsdevel@...r.kernel.org,
linux-block@...r.kernel.org, linux-mm@...ck.org,
gost.dev@...sung.com, p.raghav@...sung.com, da.gomez@...sung.com,
syzbot+f3c6fda1297c748a7076@...kaller.appspotmail.com
Subject: Re: [PATCH v2 1/8] migrate: fix skipping metadata buffer heads on
migration
On Tue, 15 Apr 2025, Luis Chamberlain wrote:
>On Tue, Apr 15, 2025 at 06:23:54PM +0200, Jan Kara wrote:
>> So I don't like removing that commit because it makes a
>> "reproducible with a heavy stress test" problem become a "reproduced by
>> real world workloads" problem.
>
>So how about just patch 2 and 8 in this series, with the spin lock
>removal happening on the last patch for Linus tree?
fyi I sent out a new series (trimmed some recipients), addressing the concerns
laid out in this approach.
https://lore.kernel.org/all/20250415231635.83960-1-dave@stgolabs.net/
Similar to adding artificial delays to a vanilla kernel, the only behavior
these modifications cause is a quicker triggering of the aforementioned
(yet independent) ext4 warning splat/corruption.
Powered by blists - more mailing lists