linux-kernel - ext3 filesystem corruption in user mode linux

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:	Fri, 24 Sep 2010 00:14:10 -0400
From:	Chris Frey <cdfrey@...rsquare.net>
To:	linux-kernel@...r.kernel.org
Subject: ext3 filesystem corruption in user mode linux

Hi,

I'm running a stock 2.6.35.4 kernel, on both the host and the guest.

For one test, I've loaded a stage3 gentoo system including portage,
created completely on the host, using dd, a 10gig sparse virtual disk,
mkfs.ext3, and the gentoo tarballs.  (I get fs corruption with Ubuntu
guests as well).

If I do some heavy CPU and disk work in the guest, something like this:

	# (cd /usr && tar cjf - portage) | tar xjf -
	# rm -rf portage

Then the filesystem corrupts itself, giving errors like the following
in dmesg, during the rm:

    EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 51715

I've posted my kernel configs online here:

	Host: http://foursquare.net/kernel/host-config.txt
	UML:  http://foursquare.net/kernel/uml-config.txt

I'm not sure what the next debugging step should be.  I can test different
versions of UML kernels, or test patches, if more testing is needed.

Thanks,
- Chris

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