diff options
author | Miklos Szeredi <mszeredi@redhat.com> | 2018-07-18 15:44:43 +0200 |
---|---|---|
committer | Miklos Szeredi <mszeredi@redhat.com> | 2018-07-18 15:44:43 +0200 |
commit | de2a4a501e716bbf5ff691ba16faf59a35320228 (patch) | |
tree | 92a505a3870fce449fab03cba16631c7cb867dc7 /init | |
parent | 8cf9ee5061037accf61775f438ad7513576d4413 (diff) | |
download | linux-stable-de2a4a501e716bbf5ff691ba16faf59a35320228.tar.gz linux-stable-de2a4a501e716bbf5ff691ba16faf59a35320228.tar.bz2 linux-stable-de2a4a501e716bbf5ff691ba16faf59a35320228.zip |
Partially revert "locks: fix file locking on overlayfs"
This partially reverts commit c568d68341be7030f5647def68851e469b21ca11.
Overlayfs files will now automatically get the correct locks, no need to
hack overlay support in VFS.
It is a partial revert, because it leaves the locks_inode() calls in place
and defines locks_inode() to file_inode(). We could revert those as well,
but it would be unnecessary code churn and it makes sense to document that
we are getting the inode for locking purposes.
Don't revert MS_NOREMOTELOCK yet since that has been part of the userspace
API for some time (though not in a useful way). Will try to remove
internal flags later when the dust around the new mount API settles.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Acked-by: Jeff Layton <jlayton@kernel.org>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions