diff options
author | Amir Goldstein <[email protected]> | 2023-11-22 14:27:12 +0200 |
---|---|---|
committer | Christian Brauner <[email protected]> | 2023-11-24 10:37:44 +0100 |
commit | 6ae654392bb516a0baa47fed1f085d84e8cad739 (patch) | |
tree | 5c8160d36c66b88636e3e1f0e39e82567c0c8976 /tools/testing/selftests/bpf/prog_tests/autoload.c | |
parent | b8e1425bae856b189e2365ff795e30fdd9e77049 (diff) |
fs: move kiocb_start_write() into vfs_iocb_iter_write()
In vfs code, sb_start_write() is usually called after the permission hook
in rw_verify_area(). vfs_iocb_iter_write() is an exception to this rule,
where kiocb_start_write() is called by its callers.
Move kiocb_start_write() from the callers into vfs_iocb_iter_write()
after the rw_verify_area() checks, to make them "start-write-safe".
The semantics of vfs_iocb_iter_write() is changed, so that the caller is
responsible for calling kiocb_end_write() on completion only if async
iocb was queued. The completion handlers of both callers were adapted
to this semantic change.
This is needed for fanotify "pre content" events.
Suggested-by: Jan Kara <[email protected]>
Suggested-by: Josef Bacik <[email protected]>
Signed-off-by: Amir Goldstein <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Reviewed-by: Josef Bacik <[email protected]>
Reviewed-by: Jan Kara <[email protected]>
Signed-off-by: Christian Brauner <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions