diff options
| author | Christoph Hellwig <[email protected]> | 2024-10-08 10:59:16 +0200 |
|---|---|---|
| committer | Carlos Maiolino <[email protected]> | 2024-10-15 11:37:42 +0200 |
| commit | acfbac776496f2093e9facf7876b4015ef8c3d1d (patch) | |
| tree | 888998290e587ee64f043b440bccb304d95aa352 /drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.c | |
| parent | 3c399374af28b158854701da324a7bff576f5a97 (diff) | |
xfs: take XFS_MMAPLOCK_EXCL xfs_file_write_zero_eof
xfs_file_write_zero_eof is the only caller of xfs_zero_range that does
not take XFS_MMAPLOCK_EXCL (aka the invalidate lock). Currently that
is actually the right thing, as an error in the iomap zeroing code will
also take the invalidate_lock to clean up, but to fix that deadlock we
need a consistent locking pattern first.
The only extra thing that XFS_MMAPLOCK_EXCL will lock out are read
pagefaults, which isn't really needed here, but also not actively
harmful.
Signed-off-by: Christoph Hellwig <[email protected]>
Reviewed-by: Darrick J. Wong <[email protected]>
Signed-off-by: Carlos Maiolino <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.c')
0 files changed, 0 insertions, 0 deletions