From: Veerabhadrarao Badiganti <vbadigan@codeaurora.org>
To: adrian.hunter@intel.com, ulf.hansson@linaro.org
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Baolin Wang <baolin.wang@linaro.org>,
Chaotian Jing <chaotian.jing@mediatek.com>,
Peng Hao <richard.peng@oppo.com>
Subject: Re: [PATCH] mmc: block: Prevent new req entering queue while freeing up the queue
Date: Tue, 3 Nov 2020 12:11:47 +0530 [thread overview]
Message-ID: <99b758d8-0fd5-2ee2-a12f-c09e71ec470b@codeaurora.org> (raw)
In-Reply-To: <1603883984-24333-1-git-send-email-vbadigan@codeaurora.org>
Hi Ulf, Adrian,
Gentle reminder. Can you share your comments on this issue and change?
Thanks
On 10/28/2020 4:49 PM, Veerabhadrarao Badiganti wrote:
> The commit bbdc74dc19e0 ("mmc: block: Prevent new req entering queue
> after its cleanup") has introduced this change but it got moved after
> del_gendisk() with commit 57678e5a3d51 ("mmc: block: Delete gendisk
> before cleaning up the request queue").
>
> It is blocking reboot with below Call stack().
>
> INFO: task reboot:3086 blocked for more than 122 seconds.
> __schedule
> schedule
> schedule_timeout
> io_schedule_timeout
> do_wait_for_common
> wait_for_completion_io
> submit_bio_wait
> blkdev_issue_flush
> ext4_sync_fs
> __sync_filesystem
> sync_filesystem
> fsync_bdev
> invalidate_partition
> del_gendisk
> mmc_blk_remove_req
> mmc_blk_remove
> mmc_bus_remove
> device_release_driver_internal
> device_release_driver
> bus_remove_device
> device_del
> mmc_remove_card
> mmc_remove
> mmc_stop_host
> mmc_remove_host
> sdhci_remove_host
> sdhci_msm_remove
> sdhci_msm_shutdown
> platform_drv_shutdown
> device_shutdown
> kernel_restart_prepare
> kernel_restart
>
> So bringing this change back.
>
> Signed-off-by: Veerabhadrarao Badiganti <vbadigan@codeaurora.org>
> ---
>
> I'm observing this issue 100% of the time with shutdown callback added to sdhci-msm driver.
> I'm trying on 5.4 kernel with ChromeOS.
>
> Please let me know if this can be fixed in a better way.
> ---
>
> drivers/mmc/core/block.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/mmc/core/block.c b/drivers/mmc/core/block.c
> index 8d3df0be0355..76dbb2b8a13b 100644
> --- a/drivers/mmc/core/block.c
> +++ b/drivers/mmc/core/block.c
> @@ -2627,6 +2627,7 @@ static void mmc_blk_remove_req(struct mmc_blk_data *md)
> * from being accepted.
> */
> card = md->queue.card;
> + blk_set_queue_dying(md->queue.queue);
> if (md->disk->flags & GENHD_FL_UP) {
> device_remove_file(disk_to_dev(md->disk), &md->force_ro);
> if ((md->area_type & MMC_BLK_DATA_AREA_BOOT) &&
next prev parent reply other threads:[~2020-11-03 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 11:19 [PATCH] mmc: block: Prevent new req entering queue while freeing up the queue Veerabhadrarao Badiganti
2020-11-03 6:41 ` Veerabhadrarao Badiganti [this message]
2020-11-03 15:25 ` Ulf Hansson
2020-11-05 7:24 ` Adrian Hunter
2020-11-11 16:22 ` Veerabhadrarao Badiganti
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=99b758d8-0fd5-2ee2-a12f-c09e71ec470b@codeaurora.org \
--to=vbadigan@codeaurora.org \
--cc=adrian.hunter@intel.com \
--cc=axboe@kernel.dk \
--cc=baolin.wang@linaro.org \
--cc=chaotian.jing@mediatek.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=richard.peng@oppo.com \
--cc=ulf.hansson@linaro.org \
/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