linux-ext4 - Add ext4__allow_read-only_mounts_with_corrupted_block_group

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 Jul 2008 19:31:26
From:	Gary Hawco <ghawco@....net>
To:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	Theodore Tso <tytso@....edu>
Subject: Add
  ext4__allow_read-only_mounts_with_corrupted_block_group_checksums patch

Ted,

Just recompiled 2.6.26 with the newest snapshot (15-July 2008/2310GMT).
uninit_bg had been enabled.

To test kernel I did: tune2fs -O ^uninit_bg /dev/sda6 to remove uninit_bg
feature.
Was prompted to run e2fsck on system.

Rebooted and e2fsck saw errors and did a forced fsck without having to
reboot. All is well thus far.

Then I did the reverse: tune2fs -O uninit_bg /dev/sda6 to renable uninit_bg
feature.
Again, I was prompted to run e2fsck on system.

Rebooted. This time I got a kernel panic that started with:
EXT4-fs: ext4_check_descriptors: Checksum for group 2 failed (10368!=32990)
EXT4-fs: group descriptors corrupted!

Then the partitions available are listed followed by
No filesystem could mount root, tried: ext4dev ext2
Kernel panic - not syncing: VFS: Unavle to mount root fs on unknown-block(8,6)

I was under the impression that the newest patch would handle this or am I
mistaken?

Thanks,
Gary

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html