From: Mark Brown <broonie@kernel.org>
To: "ȫ���� (YJ Hong)" <yj.hong@telechips.com>
Cc: "linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Possible circular locking dependency in spidev (buf_lock <-> spi_lock)
Date: Sat, 28 Feb 2026 12:55:09 +0000 [thread overview]
Message-ID: <aaLlrRjiHrr4NEIB@sirena.co.uk> (raw)
In-Reply-To: <PU4P216MB11829B6BE6520C897F0DCE0EFF70A@PU4P216MB1182.KORP216.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
On Sat, Feb 28, 2026 at 03:38:17AM +0000, ȫ���� (YJ Hong) wrote:
> Hello,
>
> I am seeing a lockdep warning in spidev reporting a possible circular
> locking dependency between buf_lock and spi_lock.
There was a change just applied to Linus' tree recently which should
avoid this, it removes buf_lock and just uses spi_lock. I guess it'll
end up in stable, not sure.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-02-28 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 3:38 [BUG] Possible circular locking dependency in spidev (buf_lock <-> spi_lock) 홍유진 (YJ Hong)
2026-02-28 12:55 ` 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=aaLlrRjiHrr4NEIB@sirena.co.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=yj.hong@telechips.com \
/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