diff options
author | Jan Kara <jack@suse.cz> | 2013-11-05 01:15:38 +0100 |
---|---|---|
committer | Jan Kara <jack@suse.cz> | 2013-11-05 11:26:47 +0100 |
commit | 7ba3ec5749ddb61f79f7be17b5fd7720eebc52de (patch) | |
tree | 01b2ff745122e12632c17142ce72748336886b03 /kernel/watchdog.c | |
parent | 18da65e7d30a76ab3ca0ccd2b7ca0690f80f28e4 (diff) | |
download | linux-stable-7ba3ec5749ddb61f79f7be17b5fd7720eebc52de.tar.gz linux-stable-7ba3ec5749ddb61f79f7be17b5fd7720eebc52de.tar.bz2 linux-stable-7ba3ec5749ddb61f79f7be17b5fd7720eebc52de.zip |
ext2: Fix fs corruption in ext2_get_xip_mem()
Commit 8e3dffc651cb "Ext2: mark inode dirty after the function
dquot_free_block_nodirty is called" unveiled a bug in __ext2_get_block()
called from ext2_get_xip_mem(). That function called ext2_get_block()
mistakenly asking it to map 0 blocks while 1 was intended. Before the
above mentioned commit things worked out fine by luck but after that commit
we started returning that we allocated 0 blocks while we in fact
allocated 1 block and thus allocation was looping until all blocks in
the filesystem were exhausted.
Fix the problem by properly asking for one block and also add assertion
in ext2_get_blocks() to catch similar problems.
Reported-and-tested-by: Andiry Xu <andiry.xu@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'kernel/watchdog.c')
0 files changed, 0 insertions, 0 deletions