> Fair enough but could you explain the potential problems? And how is > it different from sys_setpriority? Suppose you change a tasks uid in parallel with the set of conditionals in setuid - just as one example. Or you change uid _during_ a quota operation. Or during sys5 ipc ops. All of these and more make assumptions. The idea of locking uid changes with semaphores would produce some truely horrible performance impacts - 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/
- [PATCH] new setprocuid syscall BERECZ Szabolcs
- Re: [PATCH] new setprocuid syscall Peter Samuelson
- Re: [PATCH] new setprocuid syscall Martin Dalecki
- Re: [PATCH] new setprocuid syscall Peter Samuelson
- Re: [PATCH] new setprocuid syscall Alan Cox
- Re: [PATCH] new setprocuid syscall Peter Samuelson
- Re: [PATCH] new setprocuid syscall Alan Cox
- Re: [PATCH] new setprocuid syscall BERECZ Szabolcs
- Re: [PATCH] new setprocuid sysc... Peter Samuelson
- Re: [PATCH] new setprocuid sysc... Pavel Machek
- Re: [PATCH] new setprocuid syscall BERECZ Szabolcs
- Re: [PATCH] new setprocuid syscall Peter Samuelson
- Re: [PATCH] new setprocuid syscall Philipp Rumpf
- Re: [PATCH] new setprocuid syscall Petr Vandrovec
- Re: [PATCH] new setprocuid syscall Bernd Jendrissek