From: Jens Axboe <axboe@kernel.dk>
To: Dave Chinner <dchinner@redhat.com>, Jan Kara <jack@suse.cz>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Yang Yang <yang.yang@vivo.com>
Cc: stable@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH v3] block: fix deadlock between sd_remove & sd_release
Date: Wed, 24 Jul 2024 09:52:26 -0600 [thread overview]
Message-ID: <172183634626.7375.12424397192746760093.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240724070412.22521-1-yang.yang@vivo.com>
On Wed, 24 Jul 2024 15:04:12 +0800, Yang Yang wrote:
> Our test report the following hung task:
>
> [ 2538.459400] INFO: task "kworker/0:0":7 blocked for more than 188 seconds.
> [ 2538.459427] Call trace:
> [ 2538.459430] __switch_to+0x174/0x338
> [ 2538.459436] __schedule+0x628/0x9c4
> [ 2538.459442] schedule+0x7c/0xe8
> [ 2538.459447] schedule_preempt_disabled+0x24/0x40
> [ 2538.459453] __mutex_lock+0x3ec/0xf04
> [ 2538.459456] __mutex_lock_slowpath+0x14/0x24
> [ 2538.459459] mutex_lock+0x30/0xd8
> [ 2538.459462] del_gendisk+0xdc/0x350
> [ 2538.459466] sd_remove+0x30/0x60
> [ 2538.459470] device_release_driver_internal+0x1c4/0x2c4
> [ 2538.459474] device_release_driver+0x18/0x28
> [ 2538.459478] bus_remove_device+0x15c/0x174
> [ 2538.459483] device_del+0x1d0/0x358
> [ 2538.459488] __scsi_remove_device+0xa8/0x198
> [ 2538.459493] scsi_forget_host+0x50/0x70
> [ 2538.459497] scsi_remove_host+0x80/0x180
> [ 2538.459502] usb_stor_disconnect+0x68/0xf4
> [ 2538.459506] usb_unbind_interface+0xd4/0x280
> [ 2538.459510] device_release_driver_internal+0x1c4/0x2c4
> [ 2538.459514] device_release_driver+0x18/0x28
> [ 2538.459518] bus_remove_device+0x15c/0x174
> [ 2538.459523] device_del+0x1d0/0x358
> [ 2538.459528] usb_disable_device+0x84/0x194
> [ 2538.459532] usb_disconnect+0xec/0x300
> [ 2538.459537] hub_event+0xb80/0x1870
> [ 2538.459541] process_scheduled_works+0x248/0x4dc
> [ 2538.459545] worker_thread+0x244/0x334
> [ 2538.459549] kthread+0x114/0x1bc
>
> [...]
Applied, thanks!
[1/1] block: fix deadlock between sd_remove & sd_release
commit: 7e04da2dc7013af50ed3a2beb698d5168d1e594b
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-07-24 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 7:04 Yang Yang
2024-07-24 15:33 ` Christoph Hellwig
2024-07-24 15:52 ` Jens Axboe [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=172183634626.7375.12424397192746760093.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dchinner@redhat.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=stable@vger.kernel.org \
--cc=yang.yang@vivo.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
all inboxes | Powered by JetHome®