From: patchwork-bot+netdevbpf@kernel.org
To: Gustavo Luiz Duarte <gustavold@gmail.com>
Cc: leitao@debian.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
thepacketgeek@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] netconsole: Acquire su_mutex before navigating configs hierarchy
Date: Sat, 01 Nov 2025 01:00:06 +0000 [thread overview]
Message-ID: <176195880651.684055.2420166688271014327.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251029-netconsole-fix-warn-v1-1-0d0dd4622f48@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 Oct 2025 13:50:24 -0700 you wrote:
> There is a race between operations that iterate over the userdata
> cg_children list and concurrent add/remove of userdata items through
> configfs. The update_userdata() function iterates over the
> nt->userdata_group.cg_children list, and count_extradata_entries() also
> iterates over this same list to count nodes.
>
> Quoting from Documentation/filesystems/configfs.rst:
> > A subsystem can navigate the cg_children list and the ci_parent pointer
> > to see the tree created by the subsystem. This can race with configfs'
> > management of the hierarchy, so configfs uses the subsystem mutex to
> > protect modifications. Whenever a subsystem wants to navigate the
> > hierarchy, it must do so under the protection of the subsystem
> > mutex.
>
> [...]
Here is the summary with links:
- [net] netconsole: Acquire su_mutex before navigating configs hierarchy
https://git.kernel.org/netdev/net/c/d7d2fcf7ae31
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-01 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 20:50 [PATCH net] netconsole: Acquire su_mutex before navigating configs hierarchy Gustavo Luiz Duarte
2025-11-01 0:54 ` Jakub Kicinski
2025-11-01 1:00 ` patchwork-bot+netdevbpf [this message]
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=176195880651.684055.2420166688271014327.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavold@gmail.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thepacketgeek@gmail.com \
/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