From: Chris Frey <cdfrey@foursquare.net>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 filesystem corruption in user mode linux
Date: Mon, 27 Sep 2010 17:18:42 -0400 [thread overview]
Message-ID: <20100927211842.GA19667@foursquare.net> (raw)
In-Reply-To: <AANLkTinQ20uSgFP5KV17B0J0v8Y0zAg=AgAd_kf+4Bh0@mail.gmail.com>
On Mon, Sep 27, 2010 at 11:04:07PM +0200, richard -rw- weinberger wrote:
> On Fri, Sep 24, 2010 at 8:44 AM, Chris Frey <cdfrey@foursquare.net> wrote:
> > On Fri, Sep 24, 2010 at 02:05:57AM -0400, Chris Frey wrote:
> >> So far I have been unable to make 2.6.32.21 corrupt its filesystem
> >> when running as the UML kernel (Host 2.6.35.4, UML 2.6.32.21)
> >
> > Spoke too soon... 2.6.32.21 has errors too, if pushed hard enough.
> >
>
> can you do a git bisect?
I've been trying, but so far the range of buggy versions stretches back
to 2.6.32.x at least. I'm trying to find a version that doesn't have
this issue.
I'm kinda surprised that nobody else has run into this. Or maybe user
mode linux isn't used as much as I thought? Or I'm just doing something
completely bone headed. :-)
- Chris
next prev parent reply other threads:[~2010-09-27 21:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 4:14 ext3 filesystem corruption in user mode linux Chris Frey
2010-09-24 6:05 ` Chris Frey
2010-09-24 6:44 ` Chris Frey
2010-09-27 21:04 ` richard -rw- weinberger
2010-09-27 21:18 ` Chris Frey [this message]
2010-09-27 21:25 ` richard -rw- weinberger
2010-09-27 21:26 ` Chris Frey
2010-09-27 21:59 ` Chris Frey
[not found] ` <AANLkTinmCxYrjdYoDUE6+zg1i1QSJxt5ngN84FrjWJaj@mail.gmail.com>
[not found] ` <20100927221225.GA22343@foursquare.net>
[not found] ` <AANLkTi=iSSffp-48g0XAOYBSnodAsEh20j2EtHW=4Egt@mail.gmail.com>
2010-09-28 0:48 ` Chris Frey
2010-09-27 20:54 ` Chris Frey
2010-09-27 21:00 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100927211842.GA19667@foursquare.net \
--to=cdfrey@foursquare.net \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox