> > 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.. Dave. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [RFC] [PATCH 00/13] Introduce task_pid api
- From: [email protected] (Eric W. Biederman)
- Re: [RFC] [PATCH 00/13] Introduce task_pid api
- References:
- [RFC] [PATCH 00/13] Introduce task_pid api
- From: "Serge E. Hallyn" <[email protected]>
- Re: [RFC] [PATCH 00/13] Introduce task_pid api
- From: [email protected] (Eric W. Biederman)
- Re: [RFC] [PATCH 00/13] Introduce task_pid api
- From: Dave Hansen <[email protected]>
- Re: [RFC] [PATCH 00/13] Introduce task_pid api
- From: Arjan van de Ven <[email protected]>
- Re: [RFC] [PATCH 00/13] Introduce task_pid api
- From: Dave Hansen <[email protected]>
- Re: [RFC] [PATCH 00/13] Introduce task_pid api
- From: Arjan van de Ven <[email protected]>
- Re: [RFC] [PATCH 00/13] Introduce task_pid api
- From: Dave Hansen <[email protected]>
- Re: [RFC] [PATCH 00/13] Introduce task_pid api
- From: Arjan van de Ven <[email protected]>
- [RFC] [PATCH 00/13] Introduce task_pid api
- Prev by Date: [ANNOUNCE] 2.6.15-rc5-hrt2 - hrtimers based high resolution patches
- Next by Date: [PATCH 1/2] Fix ipmi_msghandler compilation without procfs
- Previous by thread: Re: [RFC] [PATCH 00/13] Introduce task_pid api
- Next by thread: Re: [RFC] [PATCH 00/13] Introduce task_pid api
- Index(es):
 |