All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
	linux-block@vger.kernel.org
Subject: Re: Blockdev 6.13-rc lockdep splat regressions
Date: Fri, 10 Jan 2025 20:13:29 +0800	[thread overview]
Message-ID: <Z4EO6YMM__e6nLNr@fedora> (raw)
In-Reply-To: <65a8ef7321bf905ab27c383395016fe299f6dfd9.camel@linux.intel.com>

On Fri, Jan 10, 2025 at 11:12:58AM +0100, Thomas Hellström wrote:
> Ming, Others
> 
> On 6.13-rc6 I'm seeing a couple of lockdep splats which appear
> introduced by the commit
> 
> f1be1788a32e ("block: model freeze & enter queue as lock for supporting
> lockdep")

The freeze lock connects all kinds of sub-system locks, that is why
we see lots of warnings after the commit is merged.

...

> #1
> [  399.006581] ======================================================
> [  399.006756] WARNING: possible circular locking dependency detected
> [  399.006767] 6.12.0-rc4+ #1 Tainted: G     U           N
> [  399.006776] ------------------------------------------------------
> [  399.006801] kswapd0/116 is trying to acquire lock:
> [  399.006810] ffff9a67a1284a28 (&q->q_usage_counter(io)){++++}-{0:0},
> at: __submit_bio+0xf0/0x1c0
> [  399.006845] 
>                but task is already holding lock:
> [  399.006856] ffffffff8a65bf00 (fs_reclaim){+.+.}-{0:0}, at:
> balance_pgdat+0xe2/0xa20
> [  399.006874] 

The above one is solved in for-6.14/block of block tree:

	block: track queue dying state automatically for modeling queue freeze lockdep

> 
> #2:
> [   81.960829] ======================================================
> [   81.961010] WARNING: possible circular locking dependency detected
> [   81.961048] 6.12.0-rc4+ #3 Tainted: G     U            

...

>                -> #3 (&q->limits_lock){+.+.}-{4:4}:
> [   81.967815]        __mutex_lock+0xad/0xb80
> [   81.968133]        nvme_update_ns_info_block+0x128/0x870 [nvme_core]
> [   81.968456]        nvme_update_ns_info+0x41/0x220 [nvme_core]
> [   81.968774]        nvme_alloc_ns+0x8a6/0xb50 [nvme_core]
> [   81.969090]        nvme_scan_ns+0x251/0x330 [nvme_core]
> [   81.969401]        async_run_entry_fn+0x31/0x130
> [   81.969703]        process_one_work+0x21a/0x590
> [   81.970004]        worker_thread+0x1c3/0x3b0
> [   81.970302]        kthread+0xd2/0x100
> [   81.970603]        ret_from_fork+0x31/0x50
> [   81.970901]        ret_from_fork_asm+0x1a/0x30
> [   81.971195] 
>                -> #2 (&q->q_usage_counter(io)){++++}-{0:0}:

The above dependency is killed by Christoph's patch.


Thanks,
Ming


  parent reply	other threads:[~2025-01-10 12:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 10:12 Blockdev 6.13-rc lockdep splat regressions Thomas Hellström
2025-01-10 10:14 ` Christoph Hellwig
2025-01-10 10:21   ` Thomas Hellström
2025-01-10 12:13 ` Ming Lei [this message]
2025-01-10 14:36   ` Thomas Hellström
2025-01-11  3:05     ` Ming Lei
2025-01-12 11:33       ` Thomas Hellström
2025-01-12 15:50         ` Ming Lei
2025-01-12 17:44           ` Thomas Hellström
2025-01-13  0:55             ` Ming Lei
2025-01-13  8:48               ` Thomas Hellström
2025-01-13  9:28         ` Ming Lei
2025-01-13  9:58           ` Thomas Hellström
2025-01-13 10:40             ` Ming Lei

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=Z4EO6YMM__e6nLNr@fedora \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=thomas.hellstrom@linux.intel.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 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.