diff options
| author | Amir Goldstein <[email protected]> | 2022-11-17 20:52:49 +0000 |
|---|---|---|
| committer | Al Viro <[email protected]> | 2022-11-25 05:52:28 +0000 |
| commit | 10bc8e4af65946b727728d7479c028742321b60a (patch) | |
| tree | aa9dfc67f7c553a2ef769623d2bd9d8cbd43f64e /lib/debugobjects.c | |
| parent | vfs: vfs_tmpfile: ensure O_EXCL flag is enforced (diff) | |
| download | kernel-10bc8e4af65946b727728d7479c028742321b60a.tar.gz kernel-10bc8e4af65946b727728d7479c028742321b60a.zip | |
vfs: fix copy_file_range() averts filesystem freeze protection
Commit 868f9f2f8e00 ("vfs: fix copy_file_range() regression in cross-fs
copies") removed fallback to generic_copy_file_range() for cross-fs
cases inside vfs_copy_file_range().
To preserve behavior of nfsd and ksmbd server-side-copy, the fallback to
generic_copy_file_range() was added in nfsd and ksmbd code, but that
call is missing sb_start_write(), fsnotify hooks and more.
Ideally, nfsd and ksmbd would pass a flag to vfs_copy_file_range() that
will take care of the fallback, but that code would be subtle and we got
vfs_copy_file_range() logic wrong too many times already.
Instead, add a flag to explicitly request vfs_copy_file_range() to
perform only generic_copy_file_range() and let nfsd and ksmbd use this
flag only in the fallback path.
This choise keeps the logic changes to minimum in the non-nfsd/ksmbd code
paths to reduce the risk of further regressions.
Fixes: 868f9f2f8e00 ("vfs: fix copy_file_range() regression in cross-fs copies")
Tested-by: Namjae Jeon <[email protected]>
Tested-by: Luis Henriques <[email protected]>
Signed-off-by: Amir Goldstein <[email protected]>
Signed-off-by: Al Viro <[email protected]>
Diffstat (limited to 'lib/debugobjects.c')
0 files changed, 0 insertions, 0 deletions