From: Tejun Heo <tj@kernel.org>
To: Roman Gushchin <guro@fb.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
kernel-team@fb.com, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] cgroup v2 freezer follow-up patches
Date: Mon, 6 May 2019 08:40:23 -0700 [thread overview]
Message-ID: <20190506154023.GP374014@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20190426175945.2559865-1-guro@fb.com>
On Fri, Apr 26, 2019 at 10:59:43AM -0700, Roman Gushchin wrote:
> Hi, Tejun!
>
> Please, pull these two follow-up patches for the cgroup v2 freezer.
>
> These are a fix for a spurious state transition, which could happen
> due to a race condition, and a cleanup of some dead code. Both patches
> were suggested by Oleg Nesterov.
Applied to cgroup/for-5.2.
Thanks.
--
tejun
prev parent reply other threads:[~2019-05-06 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 17:59 [PATCH 0/2] cgroup v2 freezer follow-up patches Roman Gushchin
2019-04-26 17:59 ` [PATCH 1/2] cgroup: prevent spurious transition into non-frozen state Roman Gushchin
2019-04-26 17:59 ` [PATCH 2/2] cgroup: get rid of cgroup_freezer_frozen_exit() Roman Gushchin
2019-05-06 15:40 ` Tejun Heo [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=20190506154023.GP374014@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).