linux-ext4 - xfstests failures w/ metadata

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]

Message-ID: <20141201202045.GR10043@birch.djwong.org>
Date:	Mon, 1 Dec 2014 12:20:45 -0800
From:	"Darrick J. Wong" <darrick.wong@...cle.com>
To:	Eric Whitney <enwlinux@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: xfstests failures w/ metadata_csum

Hi Eric,

Could you remind me which xfstests are failing in 3.18-rc3+ with metadata_csum
enabled?  I think you said generic/034, generic/321, and generic/322, but were
there more?

AFAICT the ext4 mount fails because it can't load the journal, and the journal
can't replay because jbd2_descr_block_csum_verify() fails; the 034 test appears
to drop all the writes related to the umount.  recovery.c doesn't say anything
when the journal descriptor block fails csum verification, though it should.
Not sure why we end up with corrupt-looking descriptor blocks.

The reason why this appears in -rc3 is because that's when we added the patch
that forces journal_checksum on whenever metadata_csum is on, and I guess
few people were testing journal_checksum with xfstests before that.

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