[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8333cf5e-a9cc-4b56-8b06-9b55b95e97db@I-love.SAKURA.ne.jp>
Date: Tue, 22 Jul 2025 23:04:30 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: Matthew Wilcox <willy@...radead.org>
Cc: Viacheslav Dubeyko <Slava.Dubeyko@....com>,
"glaubitz@...sik.fu-berlin.de" <glaubitz@...sik.fu-berlin.de>,
"frank.li@...o.com" <frank.li@...o.com>,
"slava@...eyko.com" <slava@...eyko.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
Subject: Re: [PATCH v3] hfs: remove BUG() from
hfs_release_folio()/hfs_test_inode()/hfs_write_inode()
On 2025/07/22 22:30, Matthew Wilcox wrote:
> On Tue, Jul 22, 2025 at 07:42:35PM +0900, Tetsuo Handa wrote:
>> I can update patch description if you have one, but I don't plan to try something like below.
>
> Why not? Papering over the underlying problem is what I rejected in v1,
> and here we are months later with you trying a v4.
Because I don't know how HFS/HFS+ filesystems work.
I just want to close these nearly 1000 days old bugs.
You can write your patches.
Powered by blists - more mailing lists