public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
	axboe@kernel.dk,
	 Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	 Linux regressions mailing list <regressions@lists.linux.dev>,
	linux-block@vger.kernel.org,  Damien Le Moal <dlemoal@kernel.org>
Subject: Re: 6.13/regression/bisected - after commit f1be1788a32e I see in the kernel log "possible circular locking dependency detected"
Date: Tue, 14 Jan 2025 11:22:47 +0500	[thread overview]
Message-ID: <CABXGCsM87Ezc9Z6TAfGaMLZsdD63O2CUyhxThoUnLw7_NmZXxA@mail.gmail.com> (raw)
In-Reply-To: <Z2I1HAKhKrCR51XO@fedora>

On Wed, Dec 18, 2024 at 7:36 AM Ming Lei <ming.lei@redhat.com> wrote:
>
> This is another deadlock caused by dependency between q->limits_lock and
> q->q_usage_counter, same with the one under discussion:
>
> https://lore.kernel.org/linux-block/20241216080206.2850773-2-ming.lei@redhat.com/
>
> The dependency of queue_limits_start_update() over blk_mq_freeze_queue()
> should be cut.
>

I see that conversation ended without sending any patches.
https://lore.kernel.org/linux-block/23008fc2-6e83-4d83-8ea1-4a3f6c0e000c@linux.ibm.com/

I am still experiencing this issue in 6.13-rc6

-- 
Best Regards,
Mike Gavrilov.

      reply	other threads:[~2025-01-14  6:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18  1:51 6.13/regression/bisected - after commit f1be1788a32e I see in the kernel log "possible circular locking dependency detected" Mikhail Gavrilov
2024-12-18  2:36 ` Ming Lei
2025-01-14  6:22   ` Mikhail Gavrilov [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=CABXGCsM87Ezc9Z6TAfGaMLZsdD63O2CUyhxThoUnLw7_NmZXxA@mail.gmail.com \
    --to=mikhail.v.gavrilov@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=regressions@lists.linux.dev \
    /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