linux-ext4 - possible bug in ext3/4 recovery

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>] [day] [month] [year] [list]

Message-Id: <F894941A-5654-4246-BDD5-A8EE4CBDD396@xyratex.com>
Date:	Thu, 25 Jul 2013 13:05:35 +0300
From:	Alexey Lyahkov <alexey_lyashkov@...atex.com>
To:	linux-ext4@...r.kernel.org
Cc:	Theodore Ts'o <tytso@....edu>,
	Andreas Dilger <Andreas.Dilger@...el.com>
Subject: possible bug in ext3/4 recovery

Hi list,

While inspecting some strange "corruptions" in Lustre servers i found situation when we try to check disk descriptors before loading/recovering a journal.
but with descriptors checksum enabled we may have a situation when we have update a checksum but don't have a real update for a descriptors because they stay in different blocks on disk. From other view both updates exist in journal and may be replayed to make in consistence.

What about moving a ext4_check_descriptors after 'no_journal' label to be sure we have check in consistence data?

----------------------------------------------
Alexey Lyahkov
alexey_lyashkov@...atex.com

--
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