[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240723144159.GB20891@lst.de>
Date: Tue, 23 Jul 2024 16:42:00 +0200
From: Christoph Hellwig <hch@....de>
To: John Garry <john.g.garry@...cle.com>
Cc: Dave Chinner <david@...morbit.com>,
"Darrick J. Wong" <djwong@...nel.org>, chandan.babu@...cle.com,
dchinner@...hat.com, hch@....de, viro@...iv.linux.org.uk,
brauner@...nel.org, jack@...e.cz, linux-xfs@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
catherine.hoang@...cle.com, martin.petersen@...cle.com
Subject: Re: [PATCH v2 07/13] xfs: Introduce FORCEALIGN inode flag
On Tue, Jul 23, 2024 at 11:11:28AM +0100, John Garry wrote:
> I am looking at something like this to implement read-only for those inodes:
Yikes. Treating individual inodes in a file systems as read-only
is about the most confusing and harmful behavior we could do.
Just treat it as any other rocompat feature please an mount the entire
file system read-only if not supported.
Or even better let this wait a little, and work with Darrick to work
on the rextsize > 1 reflіnk patches and just make the thing work.
>> So what about forcealign and RT?
>
> Any opinion on this?
What about forcealign and RT?
Powered by blists - more mailing lists