From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Christian Brauner <christian@brauner.io>,
Jack Andersen <jackoalan@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH] signal: always allocate siginfo for SI_TKILL
Date: Tue, 05 Feb 2019 00:46:28 -0600 [thread overview]
Message-ID: <8736p24trv.fsf@xmission.com> (raw)
In-Reply-To: <CAHk-=wjFUCjvFzTGNt2hNO-Q5TaQHYSD_5NDDiS+zxwf3qQPwQ@mail.gmail.com> (Linus Torvalds's message of "Tue, 5 Feb 2019 06:37:00 +0000")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Tue, Feb 5, 2019 at 2:41 AM Eric W. Biederman <ebiederm@xmission.com> wrote:
>>
>> I think the simpler change to just do:
>
> Ack. Changelog and sign-off?
Apologies I got distracted by processes ignoring SIGKILL.
I will write this up and send it out in the morning.
Eric
next prev parent reply other threads:[~2019-02-05 6:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 7:49 [PATCH] signal: always allocate siginfo for SI_TKILL Jack Andersen
2019-02-03 8:39 ` Christian Brauner
2019-02-03 18:33 ` Kees Cook
2019-02-04 15:10 ` Christian Brauner
2019-02-05 2:41 ` Eric W. Biederman
2019-02-05 6:37 ` Linus Torvalds
2019-02-05 6:46 ` Eric W. Biederman [this message]
2019-02-05 14:16 ` [PATCH] signal: Always attempt to allocate siginfo for SIGSTOP Eric W. Biederman
2019-02-05 14:49 ` Kees Cook
2019-02-05 11:23 ` [PATCH] signal: always allocate siginfo for SI_TKILL Christian Brauner
2019-02-28 4:56 ` [signal] b3eedf8d5b: BUG:unable_to_handle_kernel kernel test robot
2019-02-28 4:56 ` [LKP] " kernel test robot
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=8736p24trv.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=christian@brauner.io \
--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.