linux-kernel - Re: 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>] [day] [month] [year] [list]

Date:	Mon, 27 Sep 2010 20:48:55 -0400
From:	Chris Frey <cdfrey@...rsquare.net>
To:	richard -rw- weinberger <richard.weinberger@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: ext3 filesystem corruption in user mode linux

On Tue, Sep 28, 2010 at 01:35:09AM +0200, richard -rw- weinberger wrote:
> On Tue, Sep 28, 2010 at 12:12 AM, Chris Frey <cdfrey@...rsquare.net> wrote:
> > I'm using a mixture of the following to test.  The errors happen
> > during the 'rm'.
> >
> >        Direct copy:
> >                (cd dir && tar cjf - portage) | tar xjf - ; rm -rf portage
> >
> >        Hostfs copy:
> >                tar xjf /mnt/hostfs/portage-latest.tar.bz2 ; rm -rf portage
> >
> >        Network copy:
> >                ssh remote "cat portage-latest.tar.bz2" | tar xjf - ; rm -rf portage
> >
> > With these tests, I'm almost guessing that it might be some missed IRQs
> > or something in the guest, since files that are corrupt often contain
> > all zeros, which would match the sparse filesystem images I'm using.
> 
> Hmm, something really nasty is going one here.
> I can reproduce this issue using ext2, ext3 and reiserfs as UML root filesystem.
> It seems to be a block layer issue.
> Tomorrow I'll have a close look at the issue using my openSUSE setup.
> So far I've used your Gentoo image.

I've also seen the issue with a Ubuntu guest as well.  So far, I don't think
it matters what OS is in the guest.

Thanks for reproducing the error!
- 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/