[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <486018CB.80005@fr.ibm.com>
Date: Mon, 23 Jun 2008 23:42:35 +0200
From: Daniel Lezcano <dlezcano@...ibm.com>
To: Tejun Heo <htejun@...il.com>
CC: Benjamin Thery <benjamin.thery@...l.net>,
Greg Kroah-Hartman <gregkh@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Eric Biederman <ebiederm@...ssion.com>,
Serge Hallyn <serue@...ibm.com>, linux-kernel@...r.kernel.org,
Al Viro <viro@....linux.org.uk>,
Linux Containers <containers@...ts.osdl.org>
Subject: Re: [PATCH 05/11] sysfs: sysfs_chmod_file handle multiple superblocks
Tejun Heo wrote:
> Hello, guys. Sorry about the long silence. Recent releases of
> popular distros overwhelmed me with ata bugs. They now seem to be
> under control (and hopefully stay that way for some time to come).
>
> On the previous iteration, I was hoping I could sort out sysfs
> interface problem before this patchset but given that this is a long
> overdue feature, I think we should get this thing working first.
>
> The first four patches looked good to me, so feel free to add
> Acked-by: Tejun Heo <tj@...nel.org>
>
> Benjamin Thery Wrote:
>> sysfs: sysfs_chmod_file handle multiple superblocks
>>
>> Teach sysfs_chmod_file how to handle multiple sysfs
>> superblocks.
>
> I think it would be great if sysfs_chmod_file can do all-or-nothing
> instead of failing half way through but given the interface of
> notify_change(), it could be difficult to implement. Any ideas?
Is it acceptable to queue the notifications in a list until we are in
the loop and loop again to notify when exiting the first loop without
error ?
--
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