Re: [PATCH] regmap: Drop map lock during cache init and exit
From: Mark Brown
Date: Fri Sep 25 2026 - 08:24:29 EST
On Fri, Sep 25, 2026 at 08:43:22PM +1000, Michael Reeves via B4 Relay wrote:
> Commit fd4ebc07b4df ("regmap: Hold the regmap lock when allocating and
> freeing the cache") added the lock for Maple tree lockdep validation.
> The current Maple tree backend uses internal locking, and cache
> population is now separate from cache allocation.
Do you have a reference for what you're referencing here? The issue is
precisely that the maple tree does it's own locking with a spinlock, if
we ever use the maple tree from a hardirq context the use of the
spinlock in hardirq context will be tracked and then on removal we'll
get a locking inversion warning when we try to free it. The maple tree
locking is entirely unneeded and forces us to jump through these hoops
but there's no way to turn it off.
Attachment:
signature.asc
Description: PGP signature