Re: [PATCH 1/8] kernel/exit.c: make sure current's nsproxy != NULL while checking caps

On sob, 2015-05-23 at 12:49 -0500, Eric W. Biederman wrote: > Lukasz Pawelczyk writes: > > > There is a rare case where current's nsproxy might be NULL but we are > > required to check for credentials and capabilities. It sometimes happens > > during an exit_group() syscall while destroying user'

Re: [PATCH 1/8] kernel/exit.c: make sure current's nsproxy != NULL while checking caps

Lukasz Pawelczyk writes: > There is a rare case where current's nsproxy might be NULL but we are > required to check for credentials and capabilities. It sometimes happens > during an exit_group() syscall while destroying user's session (logging > out). > > My understanding is that while we have

[PATCH 1/8] kernel/exit.c: make sure current's nsproxy != NULL while checking caps

There is a rare case where current's nsproxy might be NULL but we are required to check for credentials and capabilities. It sometimes happens during an exit_group() syscall while destroying user's session (logging out). My understanding is that while we have to lock the task to get task's nsproxy