jdb2: Don't refuse invalidation of already invalidated buffers
authorJan Kara <jack@suse.cz>
Wed, 29 Mar 2023 15:49:32 +0000 (17:49 +0200)
committerTheodore Ts'o <tytso@mit.edu>
Fri, 14 Apr 2023 23:38:50 +0000 (19:38 -0400)
commitbd159398a2d2234de07d310132865706964aaaa7
tree2bbd16ea424fee29141d52c3dd427aa16af8eb8e
parente9ebecf266c6657de5865a02a47c0d6b2460c526
jdb2: Don't refuse invalidation of already invalidated buffers

When invalidating buffers under the partial tail page,
jbd2_journal_invalidate_folio() returns -EBUSY if the buffer is part of
the committing transaction as we cannot safely modify buffer state.
However if the buffer is already invalidated (due to previous
invalidation attempts from ext4_wait_for_tail_page_commit()), there's
nothing to do and there's no point in returning -EBUSY. This fixes
occasional warnings from ext4_journalled_invalidate_folio() triggered by
generic/051 fstest when blocksize < pagesize.

Fixes: 53e872681fed ("ext4: fix deadlock in journal_unmap_buffer()")
Signed-off-by: Jan Kara <jack@suse.cz>
Link: https://lore.kernel.org/r/20230329154950.19720-1-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
fs/jbd2/transaction.c