linux/fs/jbd2
Duane Griffin d00256766a jbd2: correctly unescape journal data blocks
Fix a long-standing typo (predating git) that will cause data corruption if a
journal data block needs unescaping.  At the moment the wrong buffer head's
data is being unescaped.

To test this case mount a filesystem with data=journal, start creating and
deleting a bunch of files containing only JBD2_MAGIC_NUMBER (0xc03b3998), then
pull the plug on the device.  Without this patch the files will contain zeros
instead of the correct data after recovery.

Signed-off-by: Duane Griffin <duaneg@dghda.com>
Acked-by: Jan Kara <jack@suse.cz>
Cc: <linux-ext4@vger.kernel.org>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-03-19 18:53:36 -07:00
..
checkpoint.c spinlock: lockbreak cleanup 2008-01-30 13:31:20 +01:00
commit.c JBD2: Clear buffer_ordered flag for barried IO request on success 2008-02-10 01:09:32 -05:00
journal.c jbd2: Mark jbd2 slabs as SLAB_TEMPORARY 2008-01-28 23:58:27 -05:00
Makefile [PATCH] jbd2: rename jbd2 symbols to avoid duplication of jbd symbols 2006-10-11 11:14:15 -07:00
recovery.c jbd2: correctly unescape journal data blocks 2008-03-19 18:53:36 -07:00
revoke.c jbd2: Mark jbd2 slabs as SLAB_TEMPORARY 2008-01-28 23:58:27 -05:00
transaction.c jbd2: sparse pointer use of zero as null 2008-01-28 23:58:27 -05:00