From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Subject: [GIT PULL] cgroup fixes for v5.6-rc5
Date: Tue, 10 Mar 2020 10:41:07 -0400 [thread overview]
Message-ID: <20200310144107.GC79873@mtj.duckdns.org> (raw)
Hello, Linus.
* cgroup.procs listing related fixes. It didn't interlock properly
with exiting tasks leaving a short window where a cgroup has empty
cgroup.procs but still can't be removed and misbehaved on short
reads.
* psi_show() crash fix on 32bit ino archs.
* Empty release_agent handling fix.
Thanks.
The following changes since commit 0bf999f9c5e74c7ecf9dafb527146601e5c848b9:
linux/pipe_fs_i.h: fix kernel-doc warnings after @wait was split (2020-02-12 11:54:08 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.6-fixes
for you to fetch changes up to 2e5383d7904e60529136727e49629a82058a5607:
cgroup1: don't call release_agent when it is "" (2020-03-04 11:53:33 -0500)
----------------------------------------------------------------
Michal Koutný (1):
cgroup: Iterate tasks that did not finish do_exit()
Qian Cai (1):
cgroup: fix psi_show() crash on 32bit ino archs
Tycho Andersen (1):
cgroup1: don't call release_agent when it is ""
Vasily Averin (2):
cgroup-v1: cgroup_pidlist_next should update position index
cgroup: cgroup_procs_next should increase position index
include/linux/cgroup.h | 1 +
kernel/cgroup/cgroup-v1.c | 3 ++-
kernel/cgroup/cgroup.c | 39 ++++++++++++++++++++++++++-------------
3 files changed, 29 insertions(+), 14 deletions(-)
--
tejun
next reply other threads:[~2020-03-10 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 14:41 Tejun Heo [this message]
2020-03-10 22:14 ` [GIT PULL] cgroup fixes for v5.6-rc5 Linus Torvalds
2020-03-12 19:25 ` Tejun Heo
2020-03-10 22:35 ` 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=20200310144107.GC79873@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).