Messages in this thread |  | | Subject | Re: [PATCH] Add user taint flag | | From | Valdis.Kletnieks@vt ... | | Date | Mon, 22 May 2006 10:29:21 -0400 |
| |
On Mon, 22 May 2006 15:35:48 BST, Alan Cox said: > On Llu, 2006-05-22 at 16:14 +0200, Arjan van de Ven wrote: > > we should then patch the /dev/mem driver or something to set this :) > > (well and possibly give it an exception for now for PCI space until the > > X people fix their stuff to use the proper sysfs stuff) > > /dev/mem is used for all sorts of sane things including DMIdecode. > Tainting on it isn't terribly useful. Mind you this whole user taint > patch seems bogus as it can only be set by root owned processes so > doesn't appear to do the job it is intended for - perhaps Ted can > explain ?
Taint on write to /dev/mem, perhaps? I don't think DMIdecode needs to scribble on /dev/mem, does it? (Figure if a userspace program runs OK on a recent Fedora or RedHat kernel, it doesn't need to scribble on /dev/mem too much, because the vast majority of it is lopped out via a patch....) [unhandled content-type:application/pgp-signature] |  |