From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>,
Eric Sandeen <sandeen@redhat.com>,
Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH v3] xfs: deprecate the V4 format
Date: Wed, 16 Sep 2020 10:07:17 +1000 [thread overview]
Message-ID: <20200916000717.GY12131@dread.disaster.area> (raw)
In-Reply-To: <20200911164311.GU7955@magnolia>
On Fri, Sep 11, 2020 at 09:43:11AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> The V4 filesystem format contains known weaknesses in the on-disk format
> that make metadata verification diffiult. In addition, the format will
> does not support dates past 2038 and will not be upgraded to do so.
> Therefore, we should start the process of retiring the old format to
> close off attack surfaces and to encourage users to migrate onto V5.
>
> Therefore, make XFS V4 support a configurable option. For the first
> period it will be default Y in case some distributors want to withdraw
> support early; for the second period it will be default N so that anyone
> who wishes to continue support can do so; and after that, support will
> be removed from the kernel.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> v3: be a little more helpful about old xfsprogs and warn more loudly
> about deprecation
> v2: define what is a V4 filesystem, update the administrator guide
> ---
> Documentation/admin-guide/xfs.rst | 23 +++++++++++++++++++++++
> fs/xfs/Kconfig | 24 ++++++++++++++++++++++++
> fs/xfs/xfs_super.c | 13 +++++++++++++
> 3 files changed, 60 insertions(+)
I agree with the overall policy direction and that we should be
warning v4 filesystem users as early as possible.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2020-09-16 0:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 16:43 [PATCH v3] xfs: deprecate the V4 format Darrick J. Wong
2020-09-14 7:29 ` Christoph Hellwig
2020-09-14 19:48 ` Eric Sandeen
2020-09-14 19:59 ` Eric Sandeen
2020-09-14 21:12 ` Darrick J. Wong
2020-09-14 21:54 ` Dave Chinner
2020-09-14 22:12 ` Eric Sandeen
2020-09-15 22:33 ` Eric Sandeen
2020-09-16 0:07 ` 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=20200916000717.GY12131@dread.disaster.area \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.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