linux-kernel - EXT3 File System Corruption 2.6.34

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: <AANLkTinQatQEYahpkN3bT-S5C41HqRoH--gTrvIbGs_c@mail.gmail.com>
Date:	Mon, 7 Jun 2010 14:45:38 -0600
From:	Jeffrey Merkey <jeffmerkey@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: EXT3 File System Corruption 2.6.34

Still seeing file system corruption after journal recovery in EXT3.
It's easy to reproduce, though the symptoms vary.  One way is to
rebuild a program and while the program is being compiled just shut
off power to the system by pulling the plug.  I am seeing the
/root/.viminfo file trashed after recovery if Vim was active during
poweroff.  I am also seeing object modules getting built which the LD
linker claims are "invalid" following a recovery event.  I suspect a
bug in the buffer cache since deleting the file still causes the old
data to be returned from buffer cache even when the sectors are
overwritten, but both are interrelated.  Seems in some way related to
EXT3 recovery which results in the buffer cache returning old sectors
and junk.

Not hard to reproduce, but the symptoms are always a little different
but the /root/.viminfo file getting nuked seems a common affect of
this bug.

Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/