diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2019-04-04 21:04:13 -0400 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2019-04-04 21:04:13 -0400 |
| commit | 9419a3191dcb27f24478d288abaab697228d28e6 (patch) | |
| tree | 7fd926e271483ad1270c5440d4839fc3711e31bb /mm/kmemleak-test.c | |
| parent | 79a3aaa7b82e3106be97842dedfd8429248896e6 (diff) | |
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 'mm/kmemleak-test.c')
0 files changed, 0 insertions, 0 deletions