On 11/26/24 12:34 AM, Damien Le Moal wrote:
Of note, is that by simply creating the scsi_debug device in a vm manually, I
get this lockdep splat:
[ 51.934109] ======================================================
[ 51.935916] WARNING: possible circular locking dependency detected
[ 51.937561] 6.12.0+ #2107 Not tainted
[ 51.938648] ------------------------------------------------------
[ 51.940351] kworker/u16:4/157 is trying to acquire lock:
[ 51.941805] ffff9fff0aa0bea8 (&q->limits_lock){+.+.}-{4:4}, at:
disk_update_zone_resources+0x86/0x170
[ 51.944314]
[ 51.944314] but task is already holding lock:
[ 51.945688] ffff9fff0aa0b890 (&q->q_usage_counter(queue)#3){++++}-{0:0}, at:
blk_revalidate_disk_zones+0x15f/0x340
[ 51.948527]
[ 51.948527] which lock already depends on the new lock.
[ 51.948527]
[ 51.951296]
[ 51.951296] the existing dependency chain (in reverse order) is:
[ 51.953708]
[ 51.953708] -> #1 (&q->q_usage_counter(queue)#3){++++}-{0:0}:
[ 51.956131] blk_queue_enter+0x1c9/0x1e0
I have disabled the blk_queue_enter() lockdep annotations locally
because these annotations cause too many false positive reports.
+DESCRIPTION="test requeuing of zoned writes and queue freezing"
There is no requeueing going on here so this description is inaccurate.
The combination of the scsi_debug options every_nth=$((2 * qd)) and
opts=0x8000 should cause requeuing, isn't it?
+ --name=pipeline-zoned-writes
Nothing is pipelined here since this is a qd=1 run.
Agreed. I will change the fio job name.
Thanks,
Bart.
