All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Francesco Dolcini <francesco.dolcini@toradex.com>
Cc: Fabio Estevam <festevam@gmail.com>,
	Daniel Vetter <daniel@ffwll.ch>, Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Sascha Hauer <kernel@pengutronix.de>,
	linux-arm-kernel@lists.infradead.org,
	NXP Linux Team <linux-imx@nxp.com>,
	Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: Regression in 5.15-rc6 - WARNING: possible circular locking dependency detected
Date: Mon, 25 Oct 2021 11:28:13 +0100	[thread overview]
Message-ID: <YXaGve1ZJq0DGZ9l@sirena.org.uk> (raw)
In-Reply-To: <20211025080229.GA11327@francesco-nb.int.toradex.com>


[-- Attachment #1.1: Type: text/plain, Size: 531 bytes --]

On Mon, Oct 25, 2021 at 10:02:29AM +0200, Francesco Dolcini wrote:

> Whoops, this seems something else already addressed here https://lore.kernel.org/all/1634886750-13861-4-git-send-email-hongxing.zhu@nxp.com/,
> sorry.

That patch looks buggy, there's a reference counting problem somewhere
which this is just papering over.  If the regulator is shared it could
drop a reference that some other device took, drivers should pretty much
never use regulator_is_enabled() except when initialising and certainly
not in cleanup paths.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2021-10-25 10:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 16:31 Regression in 5.15-rc6 - WARNING: possible circular locking dependency detected Francesco Dolcini
2021-10-24 12:09 ` Fabio Estevam
2021-10-25  7:17   ` Francesco Dolcini
2021-10-25  8:02     ` Francesco Dolcini
2021-10-25 10:28       ` 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=YXaGve1ZJq0DGZ9l@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=kernel@pengutronix.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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.