You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Eric Sandeen 9b57988db9 [PATCH] jbd2: journal_dirty_data re-check for unmapped buffers ... When running several fsx's and other filesystem stress tests, we found cases where an unmapped buffer was still being sent to submit_bh by the ext3 dirty data journaling code. I saw this happen in two ways, both related to another thread doing a truncate which would unmap the buffer in question. Either we would get into journal_dirty_data with a bh which was already unmapped (although journal_dirty_data_fn had checked for this earlier, the state was not locked at that point), or it would get unmapped in the middle of journal_dirty_data when we dropped locks to call sync_dirty_buffer. By re-checking for mapped state after we've acquired the bh state lock, we should avoid these races. If we find a buffer which is no longer mapped, we essentially ignore it, because journal_unmap_buffer has already decided that this buffer can go away. I've also added tracepoints in these two cases, and made a couple other tracepoint changes that I found useful in debugging this. Signed-off-by: Eric Sandeen <esandeen@redhat.com> Cc: <linux-ext4@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>		19 years ago
..
Makefile	…
checkpoint.c	…
commit.c	[PATCH] jbd2: switch blks_type from sector_t to ull	19 years ago
journal.c	[PATCH] null dereference in fs/jbd2/journal.c	19 years ago
recovery.c	[PATCH] jbd2: switch blks_type from sector_t to ull	19 years ago
revoke.c	[PATCH] jbd2: switch blks_type from sector_t to ull	19 years ago
transaction.c	[PATCH] jbd2: journal_dirty_data re-check for unmapped buffers	19 years ago