lkml.org 
[lkml]   [2002]   [Jan]   [4]   [last100]   RSS-feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
Complete thread (EXPERIMENTAL)
/
DateFri, 4 Jan 2002 01:18:02 -0700
FromErik Andersen <>
SubjectRe: LSB1.1: /proc/cpuinfo
Digg This
On Thu Jan 03, 2002 at 07:52:07PM -0500, Eric S. Raymond wrote:
Alexander Viro <viro@math.psu.edu>:
It's more than just a name.
a) granularity. Current "all or nothing" policy in procfs has a lot of obvious problems.
b) tree layout policy (lack thereof, to be precise). c) horribly bad layout of many, many files. Any file exported by kernel should be treated as user-visible API. As it is, common mentality is "it's a common dump; anything goes here". Inconsistent across architectures for no good reason, inconsistent across kernel versions, just plain stupid, choke-full of buffer overruns...
Fixing these problems will _hurt_. Badly. We have to do it, but it won't be fast and it certainly won't happen overnight.

I'm willing to work on this. Is there anywhere I can go to read up on current proposals before I start coding?

I once wrote up /dev/ps and /dev/mounts drivers to eliminate proc for embedded systems (pointer available if you care). It was not warmly received, but I did form some opinions in the process.
The main things to think about are
1) machine readability
Generally speaking the kernel gods have decided that ASCII is good, binary structures and such are bad (think endiannes, nfs exports, and similar oddness).
2) typing
Right now, if some /proc file prints a number, user space has to go digging about in the kernel sources to find what type that thing is -- int, uint, long, long long, etc. Cant tell without digging in the source. And what if someone then changes the type next week -- userspace then overflows.
3) field length
When coping a string from /proc (say /proc/mounts), userspace has to go digging in the kernel source to find the field length. So if I copy things into a
static buffer, I may be fine. Till someone changes the kernel to print out a bit more stuff. Then I've either got a buffer overflow (if I can't code) or a truncated string. Either way, its a problem.

So what is needed is a kernelfs virtual filesystem that provides kernel info to user space.

It needs a format that provides information as an organized directory hierarchy, which each directory and filename identifying the nature of the provided information. Files should provide information in ASCII with one value per file (to avoid all the tedious parsing), but also provides along with that bit of information type and or/length information.

In some cases I guess we may also need more complex classes on information. (lists of key-value stuff for example).
-Erik

--
Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons--
\
ISP Services
Valid XHTML 1.0!\ /
Valid CSS! Last update: 2005-03-22 12:15    [W:0.300 / U:0.270 seconds]
©2003-2005 Jasper Spaans