From: ebiederm@xmission.com (Eric W. Biederman) To: <linux-kernel@vger.kernel.org> Cc: Oleg Nesterov <oleg@redhat.com>, Linus Torvalds <torvalds@linux-foundation.org>, <linux-kernel@vger.kernel.org>, <linux-api@vger.kernel.org> Subject: [PATCH 00/10] Removing SEND_SIG_FORCED Date: Mon, 03 Sep 2018 22:41:13 +0200 [thread overview] Message-ID: <87musyl3fa.fsf@xmission.com> (raw) SEND_SIG_FORCED has two functions. It forces a pid namespace init to receive a signal it would ordinarily ignore, and it causes a siginfo to not be allocated for a signal. This patchset makes __send_signal a little bit smarter so that it can detect when to apply these optimizations and the senders of signals don't have to worry about them. The coupling of forcing a signal to the pid namespace init and not allocating siginfo resulted in serveral minor bugs where a signal sent by the kernel was marked SI_USER suggesting another userspace process sent that signal. I have cc'd linux-api in case anyone cares about these minor userspace visible differences. Unless someone notices a bug I intend to merge these changes through my tree during the next merge window. While there are numerous fixes here none of them appear to be the kind that fixes real world problems so I don't see any urgency here. Please look read and send my your review. I will be out for about a week so I will address any comments when I get back. Eric W. Biederman (10): signal: Always ignore SIGKILL and SIGSTOP sent to the global init signal: Properly deliver SIGILL from uprobes signal: Properly deliver SIGSEGV from x86 uprobes signal: Always deliver the kernel's SIGKILL and SIGSTOP to a pid namespace init signal: send_sig_all no longer needs SEND_SIG_FORCED signal: Remove the siginfo paramater from kernel_dqueue_signal signal: Don't send siginfo to kthreads. signal: Never allocate siginfo for SIGKILL or SIGSTOP signal: Use SEND_SIG_PRIV not SEND_SIG_FORCED with SIGKILL and SIGSTOP signal: Remove SEND_SIG_FORCED arch/x86/kernel/uprobes.c | 2 +- drivers/tty/sysrq.c | 2 +- drivers/usb/gadget/function/f_mass_storage.c | 4 ++-- fs/jffs2/background.c | 2 +- include/linux/sched/signal.h | 5 ++--- include/trace/events/signal.h | 3 +-- kernel/events/uprobes.c | 4 ++-- kernel/pid_namespace.c | 2 +- kernel/ptrace.c | 4 ++-- kernel/signal.c | 14 +++++++++----- mm/oom_kill.c | 4 ++-- 11 files changed, 24 insertions(+), 22 deletions(-) Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman) Cc: Oleg Nesterov <oleg@redhat.com>, Linus Torvalds <torvalds@linux-foundation.org>, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org Subject: [PATCH 00/10] Removing SEND_SIG_FORCED Date: Mon, 03 Sep 2018 22:41:13 +0200 [thread overview] Message-ID: <87musyl3fa.fsf@xmission.com> (raw) SEND_SIG_FORCED has two functions. It forces a pid namespace init to receive a signal it would ordinarily ignore, and it causes a siginfo to not be allocated for a signal. This patchset makes __send_signal a little bit smarter so that it can detect when to apply these optimizations and the senders of signals don't have to worry about them. The coupling of forcing a signal to the pid namespace init and not allocating siginfo resulted in serveral minor bugs where a signal sent by the kernel was marked SI_USER suggesting another userspace process sent that signal. I have cc'd linux-api in case anyone cares about these minor userspace visible differences. Unless someone notices a bug I intend to merge these changes through my tree during the next merge window. While there are numerous fixes here none of them appear to be the kind that fixes real world problems so I don't see any urgency here. Please look read and send my your review. I will be out for about a week so I will address any comments when I get back. Eric W. Biederman (10): signal: Always ignore SIGKILL and SIGSTOP sent to the global init signal: Properly deliver SIGILL from uprobes signal: Properly deliver SIGSEGV from x86 uprobes signal: Always deliver the kernel's SIGKILL and SIGSTOP to a pid namespace init signal: send_sig_all no longer needs SEND_SIG_FORCED signal: Remove the siginfo paramater from kernel_dqueue_signal signal: Don't send siginfo to kthreads. signal: Never allocate siginfo for SIGKILL or SIGSTOP signal: Use SEND_SIG_PRIV not SEND_SIG_FORCED with SIGKILL and SIGSTOP signal: Remove SEND_SIG_FORCED arch/x86/kernel/uprobes.c | 2 +- drivers/tty/sysrq.c | 2 +- drivers/usb/gadget/function/f_mass_storage.c | 4 ++-- fs/jffs2/background.c | 2 +- include/linux/sched/signal.h | 5 ++--- include/trace/events/signal.h | 3 +-- kernel/events/uprobes.c | 4 ++-- kernel/pid_namespace.c | 2 +- kernel/ptrace.c | 4 ++-- kernel/signal.c | 14 +++++++++----- mm/oom_kill.c | 4 ++-- 11 files changed, 24 insertions(+), 22 deletions(-) Eric
next reply other threads:[~2018-09-03 20:41 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-09-03 20:41 Eric W. Biederman [this message] 2018-09-03 20:41 ` [PATCH 00/10] Removing SEND_SIG_FORCED Eric W. Biederman 2018-09-03 20:44 ` [PATCH 01/10] signal: Always ignore SIGKILL and SIGSTOP sent to the global init Eric W. Biederman 2018-09-03 20:44 ` [PATCH 02/10] signal: Properly deliver SIGILL from uprobes Eric W. Biederman 2018-09-03 20:44 ` [PATCH 03/10] signal: Properly deliver SIGSEGV from x86 uprobes Eric W. Biederman 2018-09-03 20:44 ` [PATCH 04/10] signal: Always deliver the kernel's SIGKILL and SIGSTOP to a pid namespace init Eric W. Biederman 2018-09-03 20:44 ` [PATCH 05/10] signal: send_sig_all no longer needs SEND_SIG_FORCED Eric W. Biederman 2018-09-03 20:44 ` [PATCH 06/10] signal: Remove the siginfo paramater from kernel_dqueue_signal Eric W. Biederman 2018-09-03 20:44 ` [PATCH 07/10] signal: Don't send siginfo to kthreads Eric W. Biederman 2018-09-03 20:44 ` [PATCH 08/10] signal: Never allocate siginfo for SIGKILL or SIGSTOP Eric W. Biederman 2018-09-03 20:44 ` [PATCH 09/10] signal: Use SEND_SIG_PRIV not SEND_SIG_FORCED with SIGKILL and SIGSTOP Eric W. Biederman 2018-09-03 20:44 ` [PATCH 10/10] signal: Remove SEND_SIG_FORCED Eric W. Biederman 2018-09-08 11:03 ` [PATCH 00/10] Removing SEND_SIG_FORCED Thomas Gleixner 2018-09-16 18:04 ` [PATCH 0/4] signal: Cleanups Eric W. Biederman 2018-09-16 18:04 ` [PATCH 1/4] tty_io: Use group_send_sig_info in __do_SACK to note it is a session being killed Eric W. Biederman 2018-09-16 18:05 ` [PATCH 2/4] signal: Use group_send_sig_info to kill all processes in a pid namespace Eric W. Biederman 2018-09-16 18:06 ` [PATCH 3/4] signal: Remove specific_send_sig_info Eric W. Biederman 2018-09-16 18:06 ` [PATCH 4/4] signal: Pair exports with their functions Eric W. Biederman
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=87musyl3fa.fsf@xmission.com \ --to=ebiederm@xmission.com \ --cc=linux-api@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=oleg@redhat.com \ --cc=torvalds@linux-foundation.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.