From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v1 1/1] regmap: irq: Set lockdep class for hierarchical IRQ domains
Date: Mon, 04 Nov 2024 16:02:33 +0000 [thread overview]
Message-ID: <173073615378.64475.15494783436766249752.b4-ty@kernel.org> (raw)
In-Reply-To: <20241101165553.4055617-1-andriy.shevchenko@linux.intel.com>
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
prev parent reply other threads:[~2024-11-04 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 16:55 [PATCH v1 1/1] regmap: irq: Set lockdep class for hierarchical IRQ domains Andy Shevchenko
2024-11-04 16:02 ` Mark Brown [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=173073615378.64475.15494783436766249752.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox