[lkml]   [2014]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v9 11/11] seccomp: implement SECCOMP_FILTER_FLAG_TSYNC
First of all, sorry for delay ;)

So far I quickly glanced at this series and everything look fine, but
I am confused by the signal_group_exit() check,

On 06/27, Kees Cook wrote:
> To make sure that de_thread() is actually able
> to kill other threads during an exec, any sighand holders need to check
> if they've been scheduled to be killed, and to give up on their work.

Probably this connects to that check below? I can't understand this...

> + /*
> + * Make sure we cannot change seccomp or nnp state via TSYNC
> + * while another thread is in the middle of calling exec.
> + */
> + if (flags & SECCOMP_FILTER_FLAG_TSYNC &&
> + mutex_lock_killable(&current->signal->cred_guard_mutex))
> + goto out_free;

-EINVAL looks a bit confusing in this case, but this is cosemtic because
userspace won't see this error-code anyway.

> spin_lock_irq(&current->sighand->siglock);
> + if (unlikely(signal_group_exit(current->signal))) {
> + /* If thread is dying, return to process the signal. */

OK, this doesn't hurt, but why?

You could check __fatal_signal_pending() with the same effect. And since
we hold this mutex, exec (de_thread) can be the source of that SIGKILL.
We take this mutex specially to avoid the race with exec.

So why do we need to abort if we race with kill() or exit_grouo() ?


 \ /
  Last update: 2014-07-09 20:41    [W:0.139 / U:3.928 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site