Thread (11 messages) flat view 11 messages, 5 authors, 2008-02-18

Re: [Patch 0/2] powerpc: avoid userspace poking to legacy ioports

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2008-02-18 21:07:52
Also in: lkml

* Super-I/O chips at 0x2e/0x2f and 0x4e/0x4f.

* Legacy PC hardware monitoring chips at 0x290-0x297.

* IPMI interface at 0x0ca3 and 0x0cab (read-only).

Please tell me which ones should be skipped on PowerPC.
Skip the whole thing. I consider that on a powerpc linux port, the
platform is responsible for telling drivers where things are (via the
device tree generally)
 
Christian, can you tell me which of these probes caused trouble for you?
quoted
quoted
And how is userland code poking at random ports different from kernel
code poking at random ports? We could move sensors-detect inside the
kernel (and I have some plan to do that) but I fail to see how this
would solve this particular problem.
It wouldn't, but at least I could NAK it or make it CONFIG_X86 :-)
The same could be done for user-space (or at the /dev/port level.)
Well, there are -other- legit usages of /dev/port...

Ben.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help