Messages in this thread | | | Subject | Re: [RFC] [PATCH 00/13] Introduce task_pid api | From | (Eric W. Biederman) | Date | Mon, 19 Dec 2005 07:04:21 -0700 |
| |
Dave Airlie <airlied@gmail.com> writes:
>> >> again the DRM layer needs an audit, I'm not entirely sure if it doesn't >> get pids from userspace. THe rest of the kernel mostly ought to cope >> just fine. >> > > Yes yet again, if you can think of it, the drm will have found a way > to do it :-) > > the drmGetClient ioctl passes pids across the user/kernel boundary, > its the only place I can see in a quick look at the interfaces.... but > it isn't used for anything as far as I can see except for the dristat > testing utility..
There are crazier cases in the kernel. Netlink is my favorite example it's default ports are the process pid and some locations in the kernel even assume you are using the default port.
Eric - 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/
| |