linux-ext4 - Re: ext4: journal has aborted

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

Message-ID: <20140703231748.GA5320@thunk.org>
Date:	Thu, 3 Jul 2014 19:17:48 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Eric Whitney <enwlinux@...il.com>
Cc:	Matteo Croce <technoboy85@...il.com>,
	David Jander <david@...tonic.nl>,
	Jaehoon Chung <jh80.chung@...sung.com>,
	"Darrick J. Wong" <darrick.wong@...cle.com>,
	linux-ext4@...r.kernel.org
Subject: Re: ext4: journal has aborted

On Thu, Jul 03, 2014 at 01:14:34PM -0400, Eric Whitney wrote:
> 
> FWIW, I've also been able to reproduce that failure scenario on an
> x86_64 KVM with raw virtio disks alone.  It's just a lot harder to
> get there with that configuration - many more trials required.

What configuration are you using when you see the failure using x86_64
KVM with raw virtio?  Is this using kvm-xfstests, or some other setup?
And which file system is getting corrupted?

Because with kvm-xfstests the root file system is a read-only
snapshot, and the "mmcblk0p3" device which you show before is clearly
not the virtio device....

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