From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: xfs_clear_incompat_log_features considered harmful?
Date: Wed, 7 Feb 2024 11:14:05 +1100 [thread overview]
Message-ID: <ZcLLTb7hZqqzdEuF@dread.disaster.area> (raw)
In-Reply-To: <20240206053011.GB6226@frogsfrogsfrogs>
On Mon, Feb 05, 2024 at 09:30:11PM -0800, Darrick J. Wong wrote:
>
> So, if I'm reading you both correctly, I'll:
>
> 1. change the log incompat handling code to clear them on umount only;
> 2. add a mount option to allow admins to permit setting of log incompat
> flags;
I'd maybe turn this aroudn the other way - mount option to disallow
it, because I think the number of use cases where we don't want
flags to be set are much smaller than the number of use cases where
it either doesn't matter or using the new features is desired.
> 3. leave the xfs_{swapext,attri}_can_use_without_log_assistance
> functions as they are in djwong-wtf so that new incompat filesystem
> features will eliminate the need for setting/clearing the log
> incompat flags
>
> Did I get that right?
Sounds mostly fine to me.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2024-02-07 0:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 23:00 xfs_clear_incompat_log_features considered harmful? Darrick J. Wong
2024-02-01 4:33 ` Christoph Hellwig
2024-02-05 1:09 ` Dave Chinner
2024-02-05 6:45 ` Christoph Hellwig
2024-02-06 5:23 ` Darrick J. Wong
2024-02-09 6:33 ` Christoph Hellwig
2024-02-06 5:30 ` Darrick J. Wong
2024-02-07 0:14 ` Dave Chinner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZcLLTb7hZqqzdEuF@dread.disaster.area \
--to=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox