From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: preserve inode versioning across remounts
Date: Wed, 15 Jul 2020 18:26:06 +1000 [thread overview]
Message-ID: <20200715082606.GG2005@dread.disaster.area> (raw)
In-Reply-To: <e8bfbbec-4cb9-0267-08eb-03580e2aedc6@redhat.com>
On Tue, Jul 14, 2020 at 03:11:34PM -0700, Eric Sandeen wrote:
> The MS_I_VERSION mount flag is exposed via the VFS, as documented
> in the mount manpages etc; see the iversion and noiversion mount
> options in mount(8).
>
> As a result, mount -o remount looks for this option in /proc/mounts
> and will only send the I_VERSION flag back in during remount it it
> is present. Since it's not there, a remount will /remove/ the
> I_VERSION flag at the vfs level, and iversion functionality is lost.
>
> xfs v5 superblocks intend to always have i_version enabled; it is
> set as a default at mount time, but is lost during remount for the
> reasons above.
>
> The generic fix would be to expose this documented option in
> /proc/mounts, but since that was rejected, fix it up again in the
> xfs remount path instead, so that at least xfs won't suffer from
> this misbehavior.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> --
>
> diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
> index 379cbff438bc..9239985571af 100644
> --- a/fs/xfs/xfs_super.c
> +++ b/fs/xfs/xfs_super.c
> @@ -1714,6 +1714,10 @@ xfs_fc_reconfigure(
> int flags = fc->sb_flags;
> int error;
>
> + /* version 5 superblocks always support version counters. */
> + if (XFS_SB_VERSION_NUM(&mp->m_sb) == XFS_SB_VERSION_5)
> + fc->sb_flags |= SB_I_VERSION;
> +
> error = xfs_fc_validate_params(new_mp);
> if (error)
> return error;
Looks fine.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2020-07-15 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 22:11 [PATCH] xfs: preserve inode versioning across remounts Eric Sandeen
2020-07-15 8:26 ` Dave Chinner [this message]
2020-07-15 18:09 ` Christoph Hellwig
2020-07-15 19:04 ` Eric Sandeen
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=20200715082606.GG2005@dread.disaster.area \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.