having a tough time explaining people that no, even if there's a component referred to as a "driver" inside, a piece of userspace software can not ultimately be at fault for a kernel panic
-
but this is running as a user whose only significant privilege is membership in the video group, and the allegation is "the new builds of the userspace video-transcode acceleration driver are making the machine reboot" (the driver's source has not changed in the new builds)
Yeah, of course. If you're not root and you can panic the kernel then either root did something very wrong or your kernel is buggy.
-
-
or the hardware is
-
Or you're an embedded system, since most embedded kernel forks have no concept of security and will happily write drivers that grant all users the equivalent of /dev/mem access.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.