From: Oleg Nesterov <oleg@redhat.com>
To: Jamie Iles <jamie.iles@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SIGNAL_UNKILLABLE and init again
Date: Mon, 14 Aug 2017 18:24:13 +0200 [thread overview]
Message-ID: <20170814162413.GC9559@redhat.com> (raw)
In-Reply-To: <20170814093124.vvpa6e7ntcukghub@cedar>
Hi Jamie,
On 08/14, Jamie Iles wrote:
>
> > > Not sure, let me think a bit more... and this is not enough anyway.
> > >
> > > perhaps we should start with this simple change, but the "real" fix
> > > needs a lot of cleanups, although I am not sure if we will ever do this.
> >
> > Okay, sounds good. I'm happy to spend more time looking at this if you
> > have suggestions - in the context of namespaces and containers this
> > seems more relevant than when it was just the system init that we were
> > protecting.
>
> Any objections to moving ahead with this patch?
Oh, sorry.
OK, lets do this simple change then try to improve this logic further.
I'm afraid you need to re-send your patch, sorry.
Oleg.
prev parent reply other threads:[~2017-08-14 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 17:39 SIGNAL_UNKILLABLE and init again Jamie Iles
2017-04-26 15:18 ` Oleg Nesterov
2017-04-27 12:16 ` Jamie Iles
2017-08-14 9:31 ` Jamie Iles
2017-08-14 16:24 ` Oleg Nesterov [this message]
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=20170814162413.GC9559@redhat.com \
--to=oleg@redhat.com \
--cc=jamie.iles@oracle.com \
--cc=linux-kernel@vger.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.