linux-kernel - Re: x86 BIOS interface for partitioning and system serial number on SGI UV

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]

Date:	Tue, 5 Aug 2008 09:53:45 -0700
From:	Greg KH <greg@...ah.com>
To:	Russ Anderson <rja@....com>
Cc:	"H. Peter Anvin" <hpa@...or.com>, mingo@...e.hu,
	tglx@...utronix.de, linux-kernel@...r.kernel.org,
	Jack Steiner <steiner@....com>
Subject: Re: x86 BIOS interface for partitioning and system serial number
	on SGI UV

On Tue, Aug 05, 2008 at 11:32:30AM -0500, Russ Anderson wrote:
> On Mon, Aug 04, 2008 at 08:54:50PM -0700, Greg KH wrote:
> > On Mon, Aug 04, 2008 at 05:59:42PM -0700, H. Peter Anvin wrote:
> > > Russ Anderson wrote:
> > >>> This really seems more that it should belong in sysfs -- 
> > >>> /sys/class/firmware presumably.
> > >> /proc/sgi_uv already exists, similar to /proc/sgi_sn on Itanium systems.
> > >> Would it be /sys/class/firmware?  Reading Documentation/sysfs-rules.txt
> > >> seems to indicate somewhere under /sys/devices, such as 
> > >> /sys/devices/system/,
> > >> but I may be wrong.
> > >
> > > /sys/class/firmware is usually where firmware-related things end up, but 
> > > gregkh is the authority on sysfs organization.
> > 
> > /sys/class/firmware has a few users, but perhaps you are thinking of
> > /sys/firmware instead?  That's probably the better place for something
> > that is not using the firmware class itself.
> 
> Hi Greg,
> 
> If /sys/firmware is the right place, that is where I will put it.
> 
> Are the rules for /sys/firmware documented?  Documentation/sysfs-rules.txt
> does not mention /sys/firmware.  It seems to indicate that /sys/class
> should only contain symlinks:

Yes, using /sys/class is when using a 'struct device', is that what you
are using, or are you stuck with "raw" kobjects?

What exactly are you wanting to place in sysfs?  That will make it
easier to determine where to put it :)

Do you have a patch showing what you are proposing?

thanks,

greg k-h
--
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/