From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: "Saarinen, Jani" <jani.saarinen@intel.com>,
"luca@coelho.fi" <luca@coelho.fi>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Regression in 6.11-rc1 in scsi/sd?
Date: Wed, 31 Jul 2024 13:22:40 +0000 [thread overview]
Message-ID: <b123b699569f3a85bcfa521b2511e9e2698f31b7.camel@intel.com> (raw)
Hi,
We're getting some lockdep splats with 6.11-rc1 in some of our older CI
machines:
<4>[ 25.357106] ======================================================
<4>[ 25.358383] WARNING: possible circular locking dependency detected
<4>[ 25.359636] 6.11.0-rc1-CI_DRM_15151-gb6f9528c7fff+ #1 Not tainted
<4>[ 25.360902] ------------------------------------------------------
<4>[ 25.362184] rc.local/609 is trying to acquire lock:
<4>[ 25.363450] ffff888102358670 (&q->limits_lock){+.+.}-{3:3}, at: queue_max_discard_sectors_store+0x8e/0x110
<4>[ 25.364798]
but task is already holding lock:
<4>[ 25.367410] ffff888102358550 (&q->sysfs_lock){+.+.}-{3:3}, at: queue_attr_store+0x45/0x90
<4>[ 25.368773]
which lock already depends on the new lock.
...during device probe. You can find the full dmesg, for example, here:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15151/fi-bsw-n3050/boot0.txt
The stackdumps seem to point to sd_probe() and sd_revalidate_disk().
Is this an known issue? Does anyone have any idea what is causing it?
--
Cheers,
Luca.
next reply other threads:[~2024-07-31 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 13:22 Coelho, Luciano [this message]
2024-08-01 0:55 ` Regression in 6.11-rc1 in scsi/sd? Shinichiro Kawasaki
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=b123b699569f3a85bcfa521b2511e9e2698f31b7.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=jani.saarinen@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luca@coelho.fi \
/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