> 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 majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: [PATCH] new setprocuid syscallBERECZ Szabolcs <szabi _at_ inf.elte.hu>
- Re: [PATCH] new setprocuid syscallPeter Samuelson <peter _at_ cadcamlab.org>
- Prev by Date: Re: kernel problems
- Next by Date: Re: kernel params
- Prev by thread: Re: [PATCH] new setprocuid syscall
- Next by thread: Re: [PATCH] new setprocuid syscall
- Indexes:[Main][Thread]