linux-kernel - Re: [PATCHSET 3/4] sysfs: divorce sysfs from kobject and driver model

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071010181618.54060d13@gondolin.boeblingen.de.ibm.com>
Date:	Wed, 10 Oct 2007 18:16:18 +0200
From:	Cornelia Huck <cornelia.huck@...ibm.com>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Greg KH <greg@...ah.com>, Tejun Heo <htejun@...il.com>,
	<ebiederm@...ssion.com>, <kay.sievers@...y.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCHSET 3/4] sysfs: divorce sysfs from kobject and driver
 model

On Wed, 10 Oct 2007 11:38:50 -0400 (EDT),
Alan Stern <stern@...land.harvard.edu> wrote:

> On Tue, 9 Oct 2007, Greg KH wrote:
> 
> > The rules for sysfs files are the following:
> > 	- one value, in text format, per file.
> > 	- no action apon open/close
> > 	- binary files are only allowed for "pass-through" type files
> > 	  that the kernel does not touch (like for firmware and pci
> > 	  config space)
> > 	- directories should be associated with a kobject where it makes
> > 	  sense (no nesting deep subdirectories without a kobject
> > 	  present)
> 
> You have to stretch this a little for the power/ subdirectory every 
> device gets.  The only kobject it corresponds to is the one in the 
> device, which already corresponds to the parent directory.

Yes, this should be "directories should be associated with a kobject or
generated by an attribute group". This way you won't get deep nesting
either.
-
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/