[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1zlcwltri.fsf_-_@fess.ebiederm.org>
Date: Thu, 28 May 2009 15:58:25 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Greg KH <gregkh@...e.de>
Cc: Kay Sievers <kay.sievers@...y.org>, Greg KH <greg@...ah.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>,
Cornelia Huck <cornelia.huck@...ibm.com>,
linux-fsdevel@...r.kernel.org,
Benjamin Thery <benjamin.thery@...l.net>,
Daniel Lezcano <dlezcano@...ibm.com>,
"Eric W. Biederman" <ebiederm@...stanetworks.com>
Subject: [PATCH 0/24] sysfs cleanups.
Greg KH <gregkh@...e.de> writes:
>> > Or are there still problems, like the "fry the ext3 boot partition" that
>> > Kay found?
>>
>> That is unrelated to Eric's patches, They just added the dump, which I
>> tried to trigger. It's not entirely clear what caused the filesytem
>> damage, but I was definitely able to reproduce the unclean shutdown
>> without any of Eric's sysfs patches.
>
> Ok.
>
> But I think Eric had some updates to some of the patches along the way,
> so a whole new respin would be good to ensure I get the correct ones.
Ok. Here is my respun patchset. I have not changed which files
we remove in a directory when we remove a non-empty directory.
Leaving that issue to be addressed another time.
To accommodate that I have respun two patches:
patch 4 sysfs: Normalize removing sysfs directories.
patch 15 sysfs: Kill sysfs_addrm_start and sysfs_addrm_finish
Killing addrm is only changed to track the previous differences.
Eric
--
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