linux-kernel - Re: [PATCH v1 1/1] regmap: irq: Set lockdep class for hierarchical IRQ domains

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <173073615378.64475.15494783436766249752.b4-ty@kernel.org>
Date: Mon, 04 Nov 2024 16:02:33 +0000
From: Mark Brown <broonie@...nel.org>
To: Matti Vaittinen <mazziesaccount@...il.com>, 
 linux-kernel@...r.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
 "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH v1 1/1] regmap: irq: Set lockdep class for hierarchical
 IRQ domains

On Fri, 01 Nov 2024 18:55:53 +0200, Andy Shevchenko wrote:
> Lockdep gives a false positive splat as it can't distinguish the lock
> which is taken by different IRQ descriptors from different IRQ chips
> that are organized in a way of a hierarchy:
> 
>    ======================================================
>    WARNING: possible circular locking dependency detected
>    6.12.0-rc5-next-20241101-00148-g9fabf8160b53 #562 Tainted: G        W
>    ------------------------------------------------------
>    modprobe/141 is trying to acquire lock:
>    ffff899446947868 (intel_soc_pmic_bxtwc:502:(&bxtwc_regmap_config)->lock){+.+.}-{4:4}, at: regmap_update_bits_base+0x33/0x90
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/1] regmap: irq: Set lockdep class for hierarchical IRQ domains
      commit: 953e549471cabc9d4980f1da2e9fa79f4c23da06

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark