From: Peng Fan <peng.fan@oss.nxp.com>
To: Michael Reeves <michael.reeves077@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
Andrew Ballance <andrewjballance@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
maple-tree@lists.infradead.org, asahi@lists.linux.dev,
linux-mm@kvack.org
Subject: Re: [PATCH v3 1/2] regmap: Remove debugfs before cache teardown
Date: Thu, 8 Oct 2026 18:46:41 +0800 [thread overview]
Message-ID: <asd0kW0o6Cn4KIgD@shlinux89> (raw)
In-Reply-To: <20261006-regcache-lifecycle-submit-v3-1-37bdd82fd47c@gmail.com>
On Tue, Oct 06, 2026 at 06:03:15PM +1100, Michael Reeves wrote:
>regmap_exit() and regmap_reinit_cache() destroy the register cache before
>removing debugfs. A concurrent debugfs cache operation can therefore
>access cache state after the backend exit callback starts freeing it.
>
>Remove debugfs before cache teardown, and clear the debugfs pointer after
>removal. During cache reinitialization, recreate debugfs only after the
>new cache initializes successfully.
>
>Signed-off-by: Michael Reeves <michael.reeves077@gmail.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2026-10-08 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 7:03 [PATCH v3 0/2] regmap: Fix cache lifecycle locking and teardown Michael Reeves via B4 Relay
2026-10-06 7:03 ` Michael Reeves
2026-10-06 7:03 ` [PATCH v3 1/2] regmap: Remove debugfs before cache teardown Michael Reeves via B4 Relay
2026-10-06 7:03 ` Michael Reeves
2026-10-08 10:46 ` Peng Fan [this message]
2026-10-06 7:03 ` [PATCH v3 2/2] regmap: Drop map lock during cache init and exit Michael Reeves via B4 Relay
2026-10-06 7:03 ` Michael Reeves
2026-10-08 10:55 ` Peng Fan
2026-10-12 23:12 ` [PATCH v3 0/2] regmap: Fix cache lifecycle locking and teardown Mark Brown
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=asd0kW0o6Cn4KIgD@shlinux89 \
--to=peng.fan@oss.nxp.com \
--cc=aliceryhl@google.com \
--cc=andrewjballance@gmail.com \
--cc=asahi@lists.linux.dev \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=michael.reeves077@gmail.com \
--cc=rafael@kernel.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.