[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac3eb2510905260927we3c748akbbcaf3f3ac1da096@mail.gmail.com>
Date: Tue, 26 May 2009 18:27:19 +0200
From: Kay Sievers <kay.sievers@...y.org>
To: Alan Stern <stern@...land.harvard.edu>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>,
Cornelia Huck <cornelia.huck@...ibm.com>,
linux-fsdevel@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...stanetworks.com>
Subject: Re: [PATCH 25/20] sysfs: Only support removing emtpy sysfs
directories.
On Mon, May 25, 2009 at 13:45, Kay Sievers <kay.sievers@...y.org> wrote:
> On Mon, May 25, 2009 at 04:06, Alan Stern <stern@...land.harvard.edu> wrote:
>> by the way -- so it's a little difficult to trigger.
>
> I can trigger it pretty reliable now on plain -rc7 , but only with
> more hubs in-between the storage device. It usually take less than
> 10-15 connect/disconnect cycles.
>
> It looks like a serious bug though, after the bug triggered, random,
> likely unrelated, applications crash, and I can not cleanly shot down
> anymore.
Just a heads up if anybody is trying to reproduce this, it trashed my
ext3 rootfs, which is not recoverable.
Not sure what exactly caused this, but I didn't have anything like
this for a very long time.
I tried to reproduce the issue a few times more, and it crashed random
processes after the bug triggered, like mentioned above, and the box
never shut down cleanly.
It's entirely possible, that bug causes serious issues.
Thanks,
Kay
--
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/
Powered by blists - more mailing lists