summaryrefslogtreecommitdiff
path: root/fs/internal.h
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2019-04-04 21:04:13 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2019-04-04 21:04:13 -0400
commit9419a3191dcb27f24478d288abaab697228d28e6 (patch)
tree7fd926e271483ad1270c5440d4839fc3711e31bb /fs/internal.h
parent79a3aaa7b82e3106be97842dedfd8429248896e6 (diff)
downloadlwn-9419a3191dcb27f24478d288abaab697228d28e6.tar.gz
lwn-9419a3191dcb27f24478d288abaab697228d28e6.zip
acct_on(): don't mess with freeze protection
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>
Diffstat (limited to 'fs/internal.h')
-rw-r--r--fs/internal.h2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/internal.h b/fs/internal.h
index 6a8b71643af4..2e7362837a6e 100644
--- a/fs/internal.h
+++ b/fs/internal.h
@@ -89,9 +89,7 @@ extern int sb_prepare_remount_readonly(struct super_block *);
extern void __init mnt_init(void);
-extern int __mnt_want_write(struct vfsmount *);
extern int __mnt_want_write_file(struct file *);
-extern void __mnt_drop_write(struct vfsmount *);
extern void __mnt_drop_write_file(struct file *);
/*