Oleg Nesterov <oleg@xxxxxxxxxx> wrote: > No, only current can change ->blocked. This is even documented in > sigprocmask(). And more, the only correct way to change ->blocked > is set_current_blocked(). OK, with a couple of "I know what I am > doing" exceptions in kernel/signal.c. I was looking at force_sig_info() and derivatives. Is that what you refer to? If so, is it worth providing a force_sig_info_current(), force_sigsegv_current() and force_sig_current() to make things clearer to grep for, I wonder? David -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
