From: Greg KH <gregkh@linuxfoundation.org>
To: Zxyan Zhu <zxyan0222@gmail.com>
Cc: Mark Brown <broonie@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: debugfs: fix race condition in dummy name allocation
Date: Wed, 8 Apr 2026 15:33:01 +0200 [thread overview]
Message-ID: <2026040834-runaround-glass-8ea6@gregkh> (raw)
In-Reply-To: <20260408131155.2946395-1-zxyan0222@gmail.com>
On Wed, Apr 08, 2026 at 09:11:55PM +0800, Zxyan Zhu wrote:
> Use IDA instead of a simple counter for generating unique dummy names.
> The previous implementation used dummy_index++ which is not atomic,
> leading to potential duplicate names when multiple threads call
> regmap_debugfs_init() concurrently with name="dummy".
What code does that? Why not fix that?
Also, you did not sign off on this, so it can't be taken, sorry.
greg k-h
next prev parent reply other threads:[~2026-04-08 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 13:11 [PATCH] regmap: debugfs: fix race condition in dummy name allocation Zxyan Zhu
2026-04-08 13:33 ` Greg KH [this message]
2026-04-09 3:50 ` [PATCH v2] " Zxyan Zhu
2026-04-09 5:39 ` Greg Kroah-Hartman
2026-04-09 19:51 ` Mark Brown
2026-04-09 6:10 ` [PATCH] " zhu xin
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=2026040834-runaround-glass-8ea6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zxyan0222@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