Linux cgroups development
 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.12-rc5
Date: Tue, 29 Oct 2024 14:48:47 -1000	[thread overview]
Message-ID: <ZyGCb34Fcj3yoVL2@slm.duckdns.org> (raw)

The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:

  Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 3cc4e13bb1617f6a13e5e6882465984148743cf4:

  cgroup: Fix potential overflow issue when checking max_depth (2024-10-14 13:39:25 -1000)

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

- cgroup_bpf_release_fn() could saturate system_wq with
  cgrp->bpf.release_work which can then form a circular dependency leading
  to deadlocks. Fix by using a dedicated workqueue. The system_wq's max
  concurrency limit is being increased separately.

- Fix theoretical off-by-one bug when enforcing max cgroup hierarchy depth.

----------------------------------------------------------------
Chen Ridong (1):
      cgroup/bpf: use a dedicated workqueue for cgroup bpf destruction

Xiu Jianfeng (1):
      cgroup: Fix potential overflow issue when checking max_depth

 kernel/bpf/cgroup.c    | 19 ++++++++++++++++++-
 kernel/cgroup/cgroup.c |  4 ++--
 2 files changed, 20 insertions(+), 3 deletions(-)

--
tejun

             reply	other threads:[~2024-10-30  0:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30  0:48 Tejun Heo [this message]
2024-10-30  2:44 ` [GIT PULL] cgroup: Fixes for v6.12-rc5 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=ZyGCb34Fcj3yoVL2@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