mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v6.4-rc5
Date: Thu, 8 Jun 2023 15:01:18 -1000	[thread overview]
Message-ID: <ZIJ53jQAPxEXF-iu@slm.duckdns.org> (raw)

The following changes since commit 44c026a73be8038f03dbdeef028b642880cf1511:

  Linux 6.4-rc3 (2023-05-21 14:05:48 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git/ tags/cgroup-for-6.4-rc5-fixes

for you to fetch changes up to 5647e53f7856bb39dae781fe26aa65a699e2fc9f:

  cgroup: Documentation: Clarify usage of memory limits (2023-06-05 14:08:12 -1000)

----------------------------------------------------------------
cgroup: Fixes for v6.4-rc5

* Fix css_set reference leaks on fork failures.

* Fix CPU hotplug locking in cgroup_transfer_tasks() which is used by
  cgroup1 cpuset.

* Doc update.

----------------------------------------------------------------
Dan Schatzberg (1):
      cgroup: Documentation: Clarify usage of memory limits

John Sperbeck (1):
      cgroup: always put cset in cgroup_css_set_put_fork

Qi Zheng (1):
      cgroup: fix missing cpus_read_{lock,unlock}() in cgroup_transfer_tasks()

 Documentation/admin-guide/cgroup-v2.rst | 22 ++++++++++------------
 kernel/cgroup/cgroup-v1.c               |  4 ++--
 kernel/cgroup/cgroup.c                  | 17 ++++++++---------
 3 files changed, 20 insertions(+), 23 deletions(-)

             reply	other threads:[~2023-06-09  1:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  1:01 Tejun Heo [this message]
2023-06-09  2:24 ` 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=ZIJ53jQAPxEXF-iu@slm.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

all inboxes | Powered by JetHome®