diff options
| author | Filipe Manana <[email protected]> | 2024-08-02 09:38:51 +0100 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2024-08-02 22:32:40 +0200 |
| commit | e0391e92f9ab4fb3dbdeb139c967dcfa7ac4b115 (patch) | |
| tree | 422de414be47ecb4f421f3aac3a9cc572a47a656 /tools/testing/selftests/bpf/progs/test_prog_array_init.c | |
| parent | 1e7bec1f7d6533f08bc1c4ee94930c02361db86c (diff) | |
btrfs: fix double inode unlock for direct IO sync writes
If we do a direct IO sync write, at btrfs_sync_file(), and we need to skip
inode logging or we get an error starting a transaction or an error when
flushing delalloc, we end up unlocking the inode when we shouldn't under
the 'out_release_extents' label, and then unlock it again at
btrfs_direct_write().
Fix that by checking if we have to skip inode unlocking under that label.
Reported-by: [email protected]
Link: https://lore.kernel.org/linux-btrfs/[email protected]/
Fixes: 939b656bc8ab ("btrfs: fix corruption after buffer fault in during direct IO append write")
Reviewed-by: Josef Bacik <[email protected]>
Signed-off-by: Filipe Manana <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/progs/test_prog_array_init.c')
0 files changed, 0 insertions, 0 deletions