From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Roman Gushchin <guro@fb.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: [GIT PULL] cgroup fix for v5.2-rc1
Date: Thu, 16 May 2019 15:38:10 -0700 [thread overview]
Message-ID: <20190516223752.GE374014@devbig004.ftw2.facebook.com> (raw)
Hello, Linus.
The cgroup2 freezer pulled in this cycle broke strace. This pull
request includes a workaround for the problem. It's not a complete
fix in that it may cause spurious frozen state flip-flops which is
fairly minor. Will push a full fix once it's ready.
Thanks.
The following changes since commit 8c05f3b965da14e7790711026b32cc10a4c06213:
Merge tag 'for-linus' of git://git.armlinux.org.uk/~rmk/linux-arm (2019-05-16 09:41:54 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.2-fixes
for you to fetch changes up to 05b289263772b0698589abc47771264a685cd365:
signal: unconditionally leave the frozen state in ptrace_stop() (2019-05-16 10:43:58 -0700)
----------------------------------------------------------------
Roman Gushchin (1):
signal: unconditionally leave the frozen state in ptrace_stop()
kernel/signal.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/signal.c b/kernel/signal.c
index c4dd66436fc5..a1eb44dc9ff5 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -2113,6 +2113,7 @@ static void ptrace_stop(int exit_code, int why, int clear_code, kernel_siginfo_t
preempt_enable_no_resched();
cgroup_enter_frozen();
freezable_schedule();
+ cgroup_leave_frozen(true);
} else {
/*
* By the time we got the lock, our tracer went away.
--
tejun
next reply other threads:[~2019-05-16 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 22:38 Tejun Heo [this message]
2019-05-17 2:25 ` pr-tracker-bot
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=20190516223752.GE374014@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=guro@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®