Messages in this thread | | | Subject | Re: syscall: sys_promote | From | Trond Myklebust <> | Date | Mon, 29 Aug 2005 09:15:09 -0700 |
| |
må den 29.08.2005 Klokka 13:29 (+0100) skreiv Alan Cox: > You can ignore the patch easily enough. Ignoring the locking doesn't > work because functionality like fork process counting, exec, and setuid > all make definite assumptions that are not safe to tamper without unless > you fix the uid locking. > > Fixing it might be useful in some obscure cases anyway - POSIX threads > might benefit from it too, providing the functionality of changing all > thread uids at once isnt triggered for sensible threaded app behaviour.
The latter needs more than just locking fixes. Right now we have some potentially _very_ interesting behaviour due to the fact that large swathes of kernel code assume that a thread's privileges will not change while it is inside a syscall. This was something I started to try to address with the BSD credential patches a couple of years ago, but I never managed to finish those in time for 2.6.0.
Cheers, Trond
- 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/
| |