![]() | |||||||||||
Messages in this thread |
>> > 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 > lm-sensors looks like it pokes (writes) to /dev/mem trying to figure out some devices. >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....) > And what about /dev/port? That can also screw up things, so should probably be included in the taint unless I am missing something. Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2006-05-22 20:59 [from the cache] ©2003-2008 | |||||||||||