linux-kernel - Re: Documentation for sysfs, hotplug, and firmware loading.

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: <200707251528.36130.rob@landley.net>
Date:	Wed, 25 Jul 2007 15:28:35 -0400
From:	Rob Landley <rob@...dley.net>
To:	Greg KH <greg@...ah.com>
Cc:	Bodo Eggert <7eggert@....de>,
	Cornelia Huck <cornelia.huck@...ibm.com>,
	linux-kernel@...r.kernel.org, Michael-Luke Jones <mlj28@....ac.uk>,
	Krzysztof Halasa <khc@...waw.pl>,
	Rod Whitby <rod@...tby.id.au>,
	Russell King <rmk@....linux.org.uk>, david@...g.hm
Subject: Re: Documentation for sysfs, hotplug, and firmware loading.

On Tuesday 24 July 2007 2:38:18 am Greg KH wrote:
> > In other words: Grasping sysfs is not a feasible task? If this is true,
> > how can anybody reliably use sysfs?
>
> Huh, I never stated that at all.  If you wish to fully document sysfs
> and how it works, then great, do that.  But that was not the stated
> intent of this document, and is why I think the author got confused as
> he was attempting to put a narrow portion of how sysfs works as a
> reflection on how the whole of the body works.

I am often confused.  Confusion is my natural state.  It's how I got started 
writing documentation, as "notes to me" so I'd be able to reproduce what I 
did.

Currently my "one more thing to research before I can write this up" is your 
earlier comment that I can coldplug the existing set of devices without 
talking to sysfs.  Possibly there's a way to do this through netlink, but I 
don't know of any way to send data _back_ to the kernel with the usermode 
helper mechanism, and telling the kernel to do that for every device in the 
system at once seems like a fork bomb waiting to happen anyway.

Yes, some embedded developers want to remove the networking layer from the 
kernel, meaning they can't use netlink, meaning if we ever _do_ go to 
dynamically allocated /dev nodes and you _must_ populate /dev by getting the 
numbers out of the kernel, this is an issue.

So far, I've been able to devote about 15 minutes to this topic since the 
weekend, and that was stolen from something else...

> thanks,
>
> greg k-h

Rob

-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.
-
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/