From: Roman Gushchin <guro@fb.com>
To: Oleg Nesterov <oleg@redhat.com>, Tejun Heo <tj@kernel.org>
Cc: Tejun Heo <tj@kernel.org>, Alex Xu <alex_y_xu@yahoo.ca>,
Kernel Team <Kernel-team@fb.com>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] signal: don't always leave task frozen after ptrace_stop()
Date: Wed, 15 May 2019 17:03:44 +0000 [thread overview]
Message-ID: <20190515170336.GA9307@castle> (raw)
In-Reply-To: <20190515144335.GC18892@redhat.com>
On Wed, May 15, 2019 at 04:43:35PM +0200, Oleg Nesterov wrote:
> On 05/14, Roman Gushchin wrote:
> >
> > I agree that "may_remain_frozen" adds a lot of ugliness, so let's fix
> > the regression with the unconditional leave_frozen(true). The patch below.
> > Please, let me know if it's not what you meant.
>
> Yes, thanks, this is what I meant. Feel free to add my ACK.
Thanks!
Tejun, can you, please, pull the patch?
Thank you!
Roman
prev parent reply other threads:[~2019-05-15 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 19:55 [PATCH] signal: don't always leave task frozen after ptrace_stop() Roman Gushchin
2019-05-13 19:55 ` Roman Gushchin
2019-05-14 16:01 ` Oleg Nesterov
2019-05-14 17:46 ` Roman Gushchin
2019-05-15 14:43 ` Oleg Nesterov
2019-05-15 17:03 ` Roman Gushchin [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=20190515170336.GA9307@castle \
--to=guro@fb.com \
--cc=Kernel-team@fb.com \
--cc=alex_y_xu@yahoo.ca \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=tj@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.