linux-ext4 - [PATCH 0/2] jbd[2]: fix long-standing data corruption bug

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:	Sat, 15 Mar 2008 18:49:43 +0000
From:	"Duane Griffin" <duaneg@...da.com>
To:	sct@...hat.com, akpm@...ux-foundation.org
Cc:	linux-ext4@...r.kernel.org, duaneg@...da.com
Subject: [PATCH 0/2] jbd[2]: fix long-standing data corruption bug

It seems we have a very long-standing typo in the journal replay magic number
unescaping code that basically means it will cause data corruption if we ever
actually use it. I think this is a candidate for the stable tree.

The following script, run on an FS mounted with data=journal, may be helpful in
reproducing and testing this bug:

#!/bin/bash

rm -rf test-dir && mkdir test-dir

for (( i=0; i != 100; i++ )); do
	printf "\xc0\x3b\x39\x98" > test-dir/$RANDOM
done

while /bin/true; do
	printf "\xc0\x3b\x39\x98" > test-dir/$RANDOM
	rm test-dir/`ls test-dir | sort -R | head -n1`
done
--
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