From: Ming Lei <ming.lei@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
syzbot+3e3f419f4a7816471838@syzkaller.appspotmail.com
Subject: Re: [PATCH] block: disable the elevator int del_gendisk
Date: Wed, 1 Jun 2022 17:07:53 +0800 [thread overview]
Message-ID: <YpcsaRDNN0LeVNny@T590> (raw)
In-Reply-To: <20220601071429.GA24431@lst.de>
On Wed, Jun 01, 2022 at 09:14:29AM +0200, Christoph Hellwig wrote:
> On Wed, Jun 01, 2022 at 03:09:26PM +0800, Ming Lei wrote:
> > > Yes, we probably need a blk_mq_quiesce_queue call like in the incremental
> > > patch below. Do you have any good reproducer, though?
> >
> > blktests block/027 should cover this.
>
> That did not trigger the problem for me.
This kind of issue is often not 100% duplicated.
>
> > > if (q->elevator) {
> > > + blk_mq_quiesce_queue(q);
> > > +
> > > mutex_lock(&q->sysfs_lock);
> > > elevator_exit(q);
> > > mutex_unlock(&q->sysfs_lock);
> > > +
> > > + blk_mq_unquiesce_queue(q);
> > > }
> > >
> >
> > I am afraid the above way may slow down disk shutdown a lot, see
> > the following commit, that is also the reason why I moved it into disk
> > release handler, when any sync io submission are done.
>
> SCSI devices that are just probed and never had a disk attached will
> not have q->elevator set and not hit this quiesce at all.
Yes, but host with hundreds of real LUNs may be shutdown slowly too
since sd_remove() won't be called in async way.
Thanks,
Ming
next prev parent reply other threads:[~2022-06-01 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 16:05 [PATCH] block: disable the elevator int del_gendisk Christoph Hellwig
2022-06-01 0:54 ` Ming Lei
2022-06-01 6:43 ` Christoph Hellwig
2022-06-01 7:09 ` Ming Lei
2022-06-01 7:14 ` Christoph Hellwig
2022-06-01 9:07 ` Ming Lei [this message]
2022-06-01 12:01 ` Christoph Hellwig
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=YpcsaRDNN0LeVNny@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=syzbot+3e3f419f4a7816471838@syzkaller.appspotmail.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