diff options
author | Jan Kara <jack@suse.com> | 2015-12-07 20:04:57 (GMT) |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2015-12-07 20:04:57 (GMT) |
commit | 2dcba4781fa3842e28f47ab23056d58cd283fca6 (patch) | |
tree | b544903601f7d249b398e309cecc818c3b4a1767 /block/compat_ioctl.c | |
parent | e74031fd7ed0989da8a80364b4d269a57e9c164a (diff) | |
download | linux-2dcba4781fa3842e28f47ab23056d58cd283fca6.tar.xz |
ext4: get rid of EXT4_GET_BLOCKS_NO_LOCK flag
When dioread_nolock mode is enabled, we grab i_data_sem in
ext4_ext_direct_IO() and therefore we need to instruct _ext4_get_block()
not to grab i_data_sem again using EXT4_GET_BLOCKS_NO_LOCK. However
holding i_data_sem over overwrite direct IO isn't needed these days. We
have exclusion against truncate / hole punching because we increase
i_dio_count under i_mutex in ext4_ext_direct_IO() so once
ext4_file_write_iter() verifies blocks are allocated & written, they are
guaranteed to stay so during the whole direct IO even after we drop
i_mutex.
So we can just remove this locking abuse and the no longer necessary
EXT4_GET_BLOCKS_NO_LOCK flag.
Signed-off-by: Jan Kara <jack@suse.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'block/compat_ioctl.c')
0 files changed, 0 insertions, 0 deletions