Commit b16503ba authored by Eric W. Biederman's avatar Eric W. Biederman

signal: send_sig_all no longer needs SEND_SIG_FORCED

Now that send_signal always delivers SEND_SIG_PRIV signals to a pid
namespace init it is no longer necessary to use SEND_SIG_FORCED when
calling do_send_sig_info to ensure that pid namespace inits are
signaled and possibly killed.  Using SEND_SIG_PRIV is sufficient.

So use SEND_SIG_PRIV so that userspace when it receives a SIGTERM can
tell that the kernel sent the signal and not some random userspace
application.

Fixes: b82c3287 ("sysrq: use SEND_SIG_FORCED instead of force_sig()")
Reviewed-by: default avatarThomas Gleixner <tglx@linutronix.de>
Signed-off-by: default avatar"Eric W. Biederman" <ebiederm@xmission.com>
parent 3597dfe0
...@@ -348,7 +348,7 @@ static void send_sig_all(int sig) ...@@ -348,7 +348,7 @@ static void send_sig_all(int sig)
if (is_global_init(p)) if (is_global_init(p))
continue; continue;
do_send_sig_info(sig, SEND_SIG_FORCED, p, PIDTYPE_MAX); do_send_sig_info(sig, SEND_SIG_PRIV, p, PIDTYPE_MAX);
} }
read_unlock(&tasklist_lock); read_unlock(&tasklist_lock);
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment