[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071030100034.64fd9d70@gondolin.boeblingen.de.ibm.com>
Date: Tue, 30 Oct 2007 10:00:34 +0100
From: Cornelia Huck <cornelia.huck@...ibm.com>
To: James Bottomley <James.Bottomley@...elEye.com>
Cc: Jeff Garzik <jeff@...zik.org>, Kay Sievers <kay.sievers@...y.org>,
Greg KH <greg@...ah.com>,
linux-scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sysfs: add filter function to groups
On Mon, 29 Oct 2007 12:29:27 -0500,
James Bottomley <James.Bottomley@...elEye.com> wrote:
> On Mon, 2007-10-29 at 13:27 -0400, Jeff Garzik wrote:
> > James Bottomley wrote:
> > > visibility and creation are the same thing, aren't they? An invisible
> > > attribute doesn't appear in the sysfs directory, so it's equivalent to
> > > the file for it not being created.
> >
> >
> > What about the case where it's visible at creation time, but then needs
> > to be made selectively invisible later on?
> >
> > That implies either a remove operation or dentry checks on each lookup?
>
> Yes, that comes with the bitmap manipulation code. There will be a way
> to add and remove runtime visibility. I just wanted to get the basic
> concept agreed to first.
But visibility always comes with creation or deletion of attributes?
Perhaps what we want is to move knowledge of the attributes to the
kobject (when attributes are created/deleted), while we decide on
visibilty of the attributes (creation/deletion of sysfs entries) based
on a filter (where visibility may change, while the attribute still
exists).
-
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