On Fri, 2021-08-20 at 12:39 -0400, Jeff Layton wrote:
> v3: slight revision to verbiage, and use pr_warn_once
>
> The first patch in this series adds a new warning that should pop on
> kernels that have mandatory locking enabled when someone mounts a
> filesystem with -o mand. The second patch removes support for mandatory
> locking altogether.
>
> What I think we probably want to do is apply the first to v5.14 before
> it ships and allow the new warning to trickle out into stable kernels.
> Then we can merge the second patch in v5.15 to go ahead and remove it.
>
> Sound like a plan?
>
> Jeff Layton (2):
> fs: warn about impending deprecation of mandatory locks
> fs: remove mandatory file locking support
>
> .../filesystems/mandatory-locking.rst | 188 --
> fs/9p/vfs_file.c | 12 --
> fs/Kconfig| 10 -
> fs/afs/flock.c| 4 -
> fs/ceph/locks.c | 3 -
> fs/gfs2/file.c| 3 -
> fs/locks.c| 116 +--
> fs/namei.c| 4 +-
> fs/namespace.c| 25 +--
> fs/nfs/file.c | 4 -
> fs/nfsd/nfs4state.c | 13 --
> fs/nfsd/vfs.c | 15 --
> fs/ocfs2/locks.c | 4 -
> fs/open.c | 8 +-
> fs/read_write.c | 7 -
> fs/remap_range.c | 10 -
> include/linux/fs.h| 84
> mm/mmap.c | 6 -
> mm/nommu.c| 3 -
> 19 files changed, 14 insertions(+), 505 deletions(-)
> delete mode 100644 Documentation/filesystems/mandatory-locking.rst
>
I went ahead and pushed this version into the locks-next branch, so we
can give it some soak time before merging.
--
Jeff Layton
