From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: security@kernel.org, "Robert O'Callahan" <robert@ocallahan.org>,
Kees Cook <keescook@chromium.org>,
Andy Lutomirski <luto@kernel.org>,
Dmitry Vyukov <dvyukov@google.com>, Kyle Huey <me@kylehuey.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] fix SIGNAL_UNKILLABLE && SIGKILL interaction
Date: Mon, 13 Nov 2017 15:53:04 +0100 [thread overview]
Message-ID: <20171113145304.GA17826@redhat.com> (raw)
In-Reply-To: <20171103184144.GA21036@redhat.com>
ping...
Dmitry confirms this actually fixes the problem reported by syzkaller
we discussed in another thread.
On 11/03, Oleg Nesterov wrote:
>
> On 11/02, Oleg Nesterov wrote:
> >
> > I need to write the changelog, and perhaps even split this small patch for
> > better documentation.
>
> OK, it is not clear if I answered Eric's concerns or not, let me send the
> patches for review anyway. I tried to document every change in signal.c.
>
> Oleg.
>
> kernel/signal.c | 18 ++++++++++--------
> 1 file changed, 10 insertions(+), 8 deletions(-)
next prev parent reply other threads:[~2017-11-13 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP045Ap9Xv67GaeskDt_gAajp1Cni_S0Z0u_vsuw_ptRUuJD6Q@mail.gmail.com>
[not found] ` <20171102160705.GA11973@redhat.com>
2017-11-03 18:41 ` [PATCH 0/3] fix SIGNAL_UNKILLABLE && SIGKILL interaction Oleg Nesterov
2017-11-03 18:42 ` [PATCH 1/3] protect the traced SIGNAL_UNKILLABLE tasks from SIGKILL Oleg Nesterov
2017-11-03 18:42 ` [PATCH 2/3] protect the SIGNAL_UNKILLABLE tasks from !sig_kernel_only() signals Oleg Nesterov
2017-11-03 18:42 ` [PATCH 3/3] remove the no longer needed SIGNAL_UNKILLABLE check in complete_signal() Oleg Nesterov
2017-11-03 19:14 ` Kees Cook
2017-11-13 14:53 ` Oleg Nesterov [this message]
2017-11-13 20:00 ` [PATCH 0/3] fix SIGNAL_UNKILLABLE && SIGKILL interaction Kyle Huey
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=20171113145304.GA17826@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=me@kylehuey.com \
--cc=robert@ocallahan.org \
--cc=security@kernel.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.