Linux cgroups development
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Tejun Heo <tj@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	reinette.chatre@intel.com, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
	rafael@kernel.org, dakr@kernel.org, hannes@cmpxchg.org,
	mkoutny@suse.com, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, eddyz87@gmail.com, shuah@kernel.org,
	jolsa@kernel.org, alan.maguire@oracle.com,
	cgroups@vger.kernel.org, bpf@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Christian Loehle <christian.loehle@arm.com>
Subject: Re: [PATCH AUTOSEL 6.12 486/486] kernfs: Use RCU to access kernfs_node::parent.
Date: Tue, 17 Nov 2026 19:19:57 -0500	[thread overview]
Message-ID: <2026-11-17-1-daily-reply-0006@kernel.org> (raw)
In-Reply-To: <c6918c4e-060a-4968-a43a-1b1cbdafd27b@arm.com>

> Sorry, my bad, this should've been to ::name, later in the series.
> Here's a lockdep:

Thanks for the splat. The fix for it is not one patch but the whole kernfs RCU
series, from 400188ae361a ("kernfs: Acquire kernfs_rwsem in
kernfs_notify_workfn().") through 741c10b096bc ("kernfs: Use RCU to access
kernfs_node::name."), plus its follow-ups. None of it is tagged for stable, and
one follow-up, 6034974e3aec ("kernfs: take kernfs_rename_lock for same-parent
renames too"), is not in 7.3 or 6.18 yet.

That is too invasive for 6.12 for a lockdep report, so I'm not queueing it. A
tested backport of the series would be considered.

-- 
Thanks,
Sasha

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Tejun Heo <tj@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	reinette.chatre@intel.com, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
	rafael@kernel.org, dakr@kernel.org, hannes@cmpxchg.org,
	mkoutny@suse.com, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, eddyz87@gmail.com, shuah@kernel.org,
	jolsa@kernel.org, alan.maguire@oracle.com,
	cgroups@vger.kernel.org, bpf@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Christian Loehle <christian.loehle@arm.com>
Subject: Re: [PATCH AUTOSEL 6.12 486/486] kernfs: Use RCU to access kernfs_node::parent.
Date: Tue, 17 Nov 2026 19:22:57 -0500	[thread overview]
Message-ID: <2026-11-17-1-daily-reply-0006@kernel.org> (raw)
Message-ID: <20261118002257.8J0Hx6m5tGzALTBeIGOqKbPOrAmprGTL6yIh9GottK4@z> (raw)
In-Reply-To: <c6918c4e-060a-4968-a43a-1b1cbdafd27b@arm.com>

> Sorry, my bad, this should've been to ::name, later in the series.
> Here's a lockdep:

Thanks for the splat. The fix for it is not one patch but the whole kernfs RCU
series, from 400188ae361a ("kernfs: Acquire kernfs_rwsem in
kernfs_notify_workfn().") through 741c10b096bc ("kernfs: Use RCU to access
kernfs_node::name."), plus its follow-ups. None of it is tagged for stable, and
one follow-up, 6034974e3aec ("kernfs: take kernfs_rename_lock for same-parent
renames too"), is not in 7.3 or 6.18 yet.

That is too invasive for 6.12 for a lockdep report, so I'm not queueing it. A
tested backport of the series would be considered.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-11-18  0:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250505223922.2682012-1-sashal@kernel.org>
2025-05-05 22:32 ` [PATCH AUTOSEL 6.12 059/486] cgroup/rstat: avoid disabling irqs for O(num_cpu) Sasha Levin
2025-05-05 22:32 ` [PATCH AUTOSEL 6.12 081/486] blk-cgroup: improve policy registration error handling Sasha Levin
2025-05-05 22:34 ` [PATCH AUTOSEL 6.12 194/486] blk-throttle: don't take carryover for prioritized processing of metadata Sasha Levin
2025-05-05 22:39 ` [PATCH AUTOSEL 6.12 486/486] kernfs: Use RCU to access kernfs_node::parent Sasha Levin
2026-11-13 12:30   ` Christian Loehle
2026-11-13 19:10     ` Sasha Levin
2026-11-17 10:51       ` Christian Loehle
2026-11-18  0:19         ` Sasha Levin [this message]
2026-11-18  0:22           ` Sasha Levin

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=2026-11-17-1-daily-reply-0006@kernel.org \
    --to=sashal@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=bpf@vger.kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=christian.loehle@arm.com \
    --cc=dakr@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=eddyz87@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=rafael@kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=x86@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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