All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	Michal Koutný <mkoutny@suse.com>,
	Waiman Long <longman@redhat.com>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] cgroup: Fixes for v7.1-rc4
Date: Fri, 22 May 2026 06:47:51 -1000	[thread overview]
Message-ID: <cff491d26895c2d56392d153592009ea@kernel.org> (raw)

Hello, Linus.

The following changes since commit 345f40166694e60db6d5cf02233814bb27ac5dec:

  cgroup/cpuset: Return only actually allocated CPUs during partition invalidation (2026-05-13 08:54:53 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git tags/cgroup-for-7.1-rc4-fixes

for you to fetch changes up to 22572dbcd3486e6c4dced877125bbf50e4e24edf:

  cgroup: rstat: relax NMI guard after switch to try_cmpxchg (2026-05-20 09:44:35 -1000)

----------------------------------------------------------------
cgroup: Fixes for v7.1-rc4

Two rstat fixes:

- Out-of-bounds access in the css_rstat_updated() BPF kfunc when called
  with an unchecked user-supplied cpu.

- Over-strict NMI guard after the recent switch to try_cmpxchg left
  sparc and ppc64 unable to queue rstat updates from NMI.

----------------------------------------------------------------
Cunlong Li (1):
      cgroup: rstat: relax NMI guard after switch to try_cmpxchg

Qing Ming (1):
      cgroup/rstat: validate cpu before css_rstat_cpu() access

 block/blk-cgroup.c     |  2 +-
 include/linux/cgroup.h |  1 +
 kernel/cgroup/rstat.c  | 37 +++++++++++++++++++++++--------------
 mm/memcontrol.c        |  6 +++---
 4 files changed, 28 insertions(+), 18 deletions(-)

Thanks.

--
tejun

             reply	other threads:[~2026-05-22 16:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 16:47 Tejun Heo [this message]
2026-05-22 23:44 ` [GIT PULL] cgroup: Fixes for v7.1-rc4 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=cff491d26895c2d56392d153592009ea@kernel.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mkoutny@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.