[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cdf6a3d8-4f5c-4fce-a93e-9b0304effcb9@wdc.com>
Date: Mon, 18 Dec 2023 15:40:42 +0000
From: Johannes Thumshirn <Johannes.Thumshirn@....com>
To: Christoph Hellwig <hch@....de>
CC: "Matthew Wilcox (Oracle)" <willy@...radead.org>, Andrew Morton
<akpm@...ux-foundation.org>, "linux-fsdevel@...r.kernel.org"
<linux-fsdevel@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-block@...r.kernel.org"
<linux-block@...r.kernel.org>
Subject: Re: [PATCH 08/14] hfsplus: Really remove hfsplus_writepage
On 18.12.23 16:04, Christoph Hellwig wrote:
> On Mon, Dec 18, 2023 at 10:41:27AM +0000, Johannes Thumshirn wrote:
>>> although I had some reason to be careful back then. hfsplus should
>>> be testable again that the hfsplus Linux port is back alive. Is there
>>> any volunteer to test hfsplus on the fsdevel list?
>>
>> What do you have in mind on that side? "Just" running it through fstests
>> and see that we don't regress here or more than that?
>
> Yeah. Back in the day I ran hfsplus through xfstests, IIRC that might
> even have been the initial motivation for supporting file systems
> that don't support sparse files. I bet a lot has regressed or isn't
> support since, though.
>
Let me see what I can do on that front over my winter vacation. As long
as there's no APFS support in Linux its the only way to exchange data
between macOS and Linux anyways, so we shouldn't break it.
Powered by blists - more mailing lists