https://bugzilla.kernel.org/show_bug.cgi?id=199183 --- Comment #4 from Theodore Tso (tytso@xxxxxxx) --- OK, I was able to replicate this on 4.15, but it's not replicating on 4.16-rc1. However, the underlying issue was NOT that inode->i_sb is NULL, but rather that s_chksum_driver (found in EXT4_SBI(inode->i_sb)->s_chksum_driver) was NULL. I'm not sure why we're not ending up calling ext4_chksum() in 4.16-rc1, but the xattr code can try to calculate a crc32c, and so we should just initialize the s_chksum_driver() unconditionally. It will make things simpler, and avoid a bunch of problems. In addition, the file system should have never been allowed to have been mounted in the first place, since one of the block allocation bitmaps overlapped with the superblock, and this means that as blocks got allocated, the superblock was getting corrupted. -- You are receiving this mail because: You are watching the assignee of the bug.
