On 6/25/18 7:16 PM, Darrick J. Wong wrote: > On Mon, Jun 25, 2018 at 07:03:57PM -0500, Eric Sandeen wrote: >> The barrier mount options have been no-ops and deprecated since >> >> 4cf4573 xfs: deprecate barrier/nobarrier mount option >> >> i.e. kernel 4.10 / December 2016, with a stated deprecation schedule >> after v4.15. Should be fair game to remove them now. >> >> Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx> >> --- >> Documentation/filesystems/xfs.txt | 4 ++-- >> fs/xfs/xfs_mount.h | 1 - >> fs/xfs/xfs_super.c | 34 ++++------------------------------ >> 3 files changed, 6 insertions(+), 33 deletions(-) >> >> >> diff --git a/Documentation/filesystems/xfs.txt b/Documentation/filesystems/xfs.txt >> index 4d9ff0a..07dbd4e 100644 >> --- a/Documentation/filesystems/xfs.txt >> +++ b/Documentation/filesystems/xfs.txt >> @@ -223,8 +223,6 @@ Deprecated Mount Options >> >> Name Removal Schedule >> ---- ---------------- >> - barrier no earlier than v4.15 >> - nobarrier no earlier than v4.15 >> >> >> Removed Mount Options >> @@ -236,6 +234,8 @@ Removed Mount Options >> ihashsize v4.0 >> irixsgid v4.0 >> osyncisdsync/osyncisosync v4.0 >> + barrier v4.18 >> + nobarrier v4.18 > > I'm not removing mount options this far into the 4.18 cycle. ;) > > 4.19, perhaps? Yeah I kinda figured. Resend V2 later? Edit on the way in and stash it for a while? V2 now? -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
