diff options
author | Amir Goldstein <amir73il@gmail.com> | 2023-11-22 15:27:12 +0300 |
---|---|---|
committer | Christian Brauner <brauner@kernel.org> | 2023-11-24 12:37:44 +0300 |
commit | 6ae654392bb516a0baa47fed1f085d84e8cad739 (patch) | |
tree | 5c8160d36c66b88636e3e1f0e39e82567c0c8976 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | b8e1425bae856b189e2365ff795e30fdd9e77049 (diff) | |
download | linux-6ae654392bb516a0baa47fed1f085d84e8cad739.tar.xz |
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 <jack@suse.cz>
Suggested-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Link: https://lore.kernel.org/r/20231122122715.2561213-14-amir73il@gmail.com
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions