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 Koutny <mkoutny@suse.com>,
	Waiman Long <longman@redhat.com>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] cgroup: Fixes for v7.3-rc4
Date: Thu, 24 Sep 2026 11:19:27 -1000	[thread overview]
Message-ID: <1e7eeebbabc3a9404fbea6928722474a@kernel.org> (raw)

Hello,

The following changes since commit 057dac23d329d5c5ed62352f2659a39fd46c6d4a:

  cgroup: Avoid iteration of dying tasks with zero refcount (2026-09-14 12:43:50 -1000)

are available in the Git repository at:

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

for you to fetch changes up to 1765a153d985c231357145e26798f9408db10e42:

  cgroup/pids: Restore pids.events notifications in local mode (2026-09-24 06:22:11 -1000)

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

- With local event accounting, a fork rejected by the pids controller
  updated pids.events without notifying its pollers.

- A cgroup selftest failed to compile with fortification enabled because
  an O_TMPFILE open lacked its mode argument.

----------------------------------------------------------------
Eva Kurchatova (1):
      selftests: cgroup: give the O_TMPFILE open in get_temp_fd() a mode

Guopeng Zhang (1):
      cgroup/pids: Restore pids.events notifications in local mode

 kernel/cgroup/pids.c                             | 5 +++++
 tools/testing/selftests/cgroup/test_memcontrol.c | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

-- 
tejun

             reply	other threads:[~2026-09-24 21:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 21:19 Tejun Heo [this message]
2026-09-24 22:05 ` [GIT PULL] cgroup: Fixes for v7.3-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=1e7eeebbabc3a9404fbea6928722474a@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.