https://bugzilla.kernel.org/show_bug.cgi?id=199947 Bug ID: 199947 Summary: Mounting and operating corrupted ext4 image causes (finite) hangs in kernel space Product: File System Version: 2.5 Kernel Version: v4.17 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: ext4 Assignee: fs_ext4@xxxxxxxxxxxxxxxxxxxx Reporter: anatoly.trosinenko@xxxxxxxxxx Regression: No Created attachment 276345 --> https://bugzilla.kernel.org/attachment.cgi?id=276345&action=edit Invalid ext4 FS image causing a bug Performing some operations on invalid ext4 partition causes hangs for about 1 second (such as "user 0m 0.00s sys 0m 1.03s") and incorrect syscall return code. How to reproduce: 1. Compile the 4.17 kernel with the attached config 2. Unpack and mount the attached FS image as ext4 (supposing, mount point is /mnt) 3. Run `time ln -s /mnt/abc /mnt/abc` What happens: [ 1.858452] EXT4-fs warning (device sda): dx_probe:754: inode #2: comm exe: Unrecognised inode hash code 220 [ 1.858670] EXT4-fs warning (device sda): dx_probe:865: inode #2: comm exe: Corrupt directory, running e2fsck is recommended [ 2.510052] EXT4-fs warning (device sda): dx_probe:754: inode #2: comm exe: Unrecognised inode hash code 220 [ 2.510280] EXT4-fs warning (device sda): dx_probe:865: inode #2: comm exe: Corrupt directory, running e2fsck is recommended ln: /mnt/abc: Unknown error 4094 [ 3.166796] exe (952) used greatest stack depth: 13664 bytes left Command exited with non-zero status 1 real 0m 1.31s user 0m 0.00s sys 0m 1.30s The (3) can be repeated any number of times with the same 1 second hang without remounting. -- You are receiving this mail because: You are watching the assignee of the bug.
