From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Eric Sandeen <sandeen@redhat.com>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] mkfs: warn about V4 deprecation when creating new V4 filesystems
Date: Tue, 31 Aug 2021 16:53:25 -0700 [thread overview]
Message-ID: <20210831235325.GD9942@magnolia> (raw)
In-Reply-To: <20210831233300.GC9942@magnolia>
On Tue, Aug 31, 2021 at 04:33:00PM -0700, Darrick J. Wong wrote:
> On Wed, Sep 01, 2021 at 09:29:27AM +1000, Dave Chinner wrote:
> > On Tue, Aug 31, 2021 at 03:44:38PM -0700, Darrick J. Wong wrote:
> > > From: Darrick J. Wong <djwong@kernel.org>
> > >
> > > The V4 filesystem format is deprecated in the upstream Linux kernel. In
> > > September 2025 it will be turned off by default in the kernel and five
> > > years after that, support will be removed entirely. Warn people
> > > formatting new filesystems with the old format, particularly since V4 is
> > > not the default.
> > >
> > > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > > ---
> > > mkfs/xfs_mkfs.c | 9 +++++++++
> > > 1 file changed, 9 insertions(+)
> > >
> > > diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> > > index 53904677..b8c11ce9 100644
> > > --- a/mkfs/xfs_mkfs.c
> > > +++ b/mkfs/xfs_mkfs.c
> > > @@ -2103,6 +2103,15 @@ _("Directory ftype field always enabled on CRC enabled filesystems\n"));
> > > }
> > >
> > > } else { /* !crcs_enabled */
> > > + /*
> > > + * The V4 filesystem format is deprecated in the upstream Linux
> > > + * kernel. In September 2025 it will be turned off by default
> > > + * in the kernel and in September 2030 support will be removed
> > > + * entirely.
> > > + */
> > > + fprintf(stdout,
> > > +_("V4 filesystems are deprecated and will not be supported by future versions.\n"));
> > > +
> > > /*
> > > * The kernel doesn't support crc=0,finobt=1 filesystems.
> > > * If crcs are not enabled and the user has not explicitly
> > >
> >
> > Looks good to me.
> >
> > Reviewed-by: Dave Chinner <dchinner@redhat.com>
> >
> > Do we need to update the mkfs filter in fstests now?
>
> AFAICT, no, because (so far) the only fstests that care about mkfs
> output only look for messages on stderr, and dump stdout to $seqres.full
> or /dev/null.
So I'll immediately put my foot in my mouth; there /was/ a patch in my
fstests tree to fix the one test that broke: xfs/449.
--D
> --D
>
> > Cheers,
> >
> > Dave.
> > --
> > Dave Chinner
> > david@fromorbit.com
prev parent reply other threads:[~2021-08-31 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 22:44 [PATCH] mkfs: warn about V4 deprecation when creating new V4 filesystems Darrick J. Wong
2021-08-31 23:29 ` Dave Chinner
2021-08-31 23:33 ` Darrick J. Wong
2021-08-31 23:53 ` Darrick J. Wong [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=20210831235325.GD9942@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).