> I don't see the problem. When they are using it without locks in user space > the behavior is undefined anyways (the set*id may have appeared before
kernel space > events (signals etc.) you don't need any additional locking neither, > because the normal locking of the task (grabbing exit_sem, task list lock > etc.) > is enough. no. People assume it cant change during a syscall
