diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2019-04-04 21:04:13 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-05-31 06:46:05 -0700 |
| commit | 7c2bcb3cca0339b73f6e1883c14f1166f233c8d9 (patch) | |
| tree | 867b77aad2f5abf0f48dcfe6c4dfb3bcf3511c45 /include/linux | |
| parent | 7d562a90a88bf96d5ab7fdb90e4aad4d05c08392 (diff) | |
| download | linux-stable-7c2bcb3cca0339b73f6e1883c14f1166f233c8d9.tar.gz linux-stable-7c2bcb3cca0339b73f6e1883c14f1166f233c8d9.tar.bz2 linux-stable-7c2bcb3cca0339b73f6e1883c14f1166f233c8d9.zip | |
acct_on(): don't mess with freeze protection
commit 9419a3191dcb27f24478d288abaab697228d28e6 upstream.
What happens there is that we are replacing file->path.mnt of
a file we'd just opened with a clone and we need the write
count contribution to be transferred from original mount to
new one. That's it. We do *NOT* want any kind of freeze
protection for the duration of switchover.
IOW, we should just use __mnt_{want,drop}_write() for that
switchover; no need to bother with mnt_{want,drop}_write()
there.
Tested-by: Amir Goldstein <amir73il@gmail.com>
Reported-by: syzbot+2a73a6ea9507b7112141@syzkaller.appspotmail.com
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/linux')
| -rw-r--r-- | include/linux/mount.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/include/linux/mount.h b/include/linux/mount.h index 45b1f56c6c2f..4b0db4418954 100644 --- a/include/linux/mount.h +++ b/include/linux/mount.h @@ -86,6 +86,8 @@ extern bool mnt_may_suid(struct vfsmount *mnt); struct path; extern struct vfsmount *clone_private_mount(const struct path *path); +extern int __mnt_want_write(struct vfsmount *); +extern void __mnt_drop_write(struct vfsmount *); struct file_system_type; extern struct vfsmount *vfs_kern_mount(struct file_system_type *type, |