http://bugzilla.kernel.org/show_bug.cgi?id=12478 Summary: Infinite loop printing "__find_get_block_slow() failed." on accessing intentionally corrupted ext4 fs Product: File System Version: 2.5 KernelVersion: 2.6.29-rc2 + the patches for #12430 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: ext4 AssignedTo: fs_ext4@xxxxxxxxxxxxxxxxxxxx ReportedBy: sliedes@xxxxxxxxx Hardware Environment: qemu x86 Software Environment: Minimal Debian sid/unstable Problem Description: Accessing the attached intentionally corrupted ext4 filesystem causes a seemingly infinite (at least _very_ long) loop where kernel floods dmesg with these messages: [ 67.126302] __find_get_block_slow() failed. block=4294967296, b_blocknr=0 [ 67.126609] b_state=0x00000020, b_size=1024 [ 67.126798] device blocksize: 1024 [ 67.126972] __find_get_block_slow() failed. block=4294967296, b_blocknr=0 [ 67.127244] b_state=0x00000020, b_size=1024 [ 67.127415] device blocksize: 1024 [ 67.127573] __find_get_block_slow() failed. block=4294967296, b_blocknr=0 [ 67.127844] b_state=0x00000020, b_size=1024 ... ad infinitum Steps to reproduce: 1. bunzip2 the attached filesystem image 2. mount hdb.153 /mnt -t ext4 -o loop,errors=continue 3. rm -rf /mnt >&/dev/null -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
