From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Subject: Re: [PATCH 25/20] sysfs: Only support removing emtpy sysfs directories. Date: Tue, 26 May 2009 18:27:19 +0200 Message-ID: References: <1243178448.4035.12.camel@poy> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "Eric W. Biederman" , Andrew Morton , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, Tejun Heo , Cornelia Huck , linux-fsdevel@vger.kernel.org, "Eric W. Biederman" To: Alan Stern Return-path: Received: from mail-fx0-f168.google.com ([209.85.220.168]:44730 "EHLO mail-fx0-f168.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754702AbZEZQ1i (ORCPT ); Tue, 26 May 2009 12:27:38 -0400 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, May 25, 2009 at 13:45, Kay Sievers wrote: > On Mon, May 25, 2009 at 04:06, Alan Stern 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