All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, Oleg Nesterov <oleg@redhat.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	Jack Andersen <jackoalan@gmail.com>,
	Christian Brauner <christian@brauner.io>,
	Kees Cook <keescook@chromium.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [GIT PULL] signal fixes for v5.0-rc6
Date: Fri, 08 Feb 2019 09:52:02 -0600	[thread overview]
Message-ID: <87mun6nuql.fsf@xmission.com> (raw)


Linus,

Please pull the for-linus branch from the git tree:

   git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-linus

   HEAD:7146db3317c67b517258cb5e1b08af387da0618b signal: Better detection of synchronous signals

This contains 4 small fixes for signal handling.  A missing range check,
a regression fix, prioritizing signals we have already started a signal
group exit for, and better detection of synchronous signals.

The confused decision of which signals to handle failed spectacularly
when a timer was pointed at SIGBUS and the stack overflowed.  Resulting
in an unkillable process in an infinite loop instead of a SIGSEGV and
core dump.

Eric W. Biederman (4):
      signal: Make siginmask safe when passed a signal of 0
      signal: Always attempt to allocate siginfo for SIGSTOP
      signal: Always notice exiting tasks
      signal: Better detection of synchronous signals

 include/linux/signal.h |  2 +-
 kernel/signal.c        | 63 ++++++++++++++++++++++++++++++++++++++++++++++----
 2 files changed, 60 insertions(+), 5 deletions(-)

Eric

             reply	other threads:[~2019-02-08 15:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 15:52 Eric W. Biederman [this message]
2019-02-09  0:40 ` [GIT PULL] signal fixes for v5.0-rc6 pr-tracker-bot
2019-02-11 16:47 ` Oleg Nesterov

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=87mun6nuql.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=christian@brauner.io \
    --cc=dvyukov@google.com \
    --cc=jackoalan@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=tglx@linutronix.de \
    --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: link
Be 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.