From: Ming Lei <ming.lei@redhat.com>
To: "jianchao.wang" <jianchao.w.wang@oracle.com>
Cc: Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@kernel.dk>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
Bart Van Assche <bart.vanassche@wdc.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH V2 1/5] block: introduce blk_quiesce_timeout() and blk_unquiesce_timeout()
Date: Wed, 2 May 2018 11:33:43 +0800 [thread overview]
Message-ID: <20180502033342.GD22363@ming.t460p> (raw)
In-Reply-To: <93c4190f-178a-a3b4-5203-bd8c6a0eaef2@oracle.com>
On Wed, May 02, 2018 at 10:23:35AM +0800, jianchao.wang wrote:
> Hi ming
>
> On 04/29/2018 11:41 PM, Ming Lei wrote:
> >
> > +static void __blk_unquiesce_timeout(struct request_queue *q)
> > +{
> > + unsigned long flags;
> > +
> > + spin_lock_irqsave(q->queue_lock, flags);
> > + q->timeout_off = false;
> > + spin_unlock_irqrestore(q->queue_lock, flags);
> > +}
> > +
> > +void blk_unquiesce_timeout(struct request_queue *q)
> > +{
> > + __blk_unquiesce_timeout(q);
> > + mod_timer(&q->timeout, jiffies + q->rq_timeout);
> > +}
> > +EXPORT_SYMBOL(blk_unquiesce_timeout);
> > +
> > +void blk_quiesce_timeout(struct request_queue *q)
> > +{
> > + unsigned long flags;
> > +
> > + spin_lock_irqsave(q->queue_lock, flags);
> > + q->timeout_off = true;
> > + spin_unlock_irqrestore(q->queue_lock, flags);
> > +
> > + del_timer_sync(&q->timeout);
> > + cancel_work_sync(&q->timeout_work);
> > +}
> > +EXPORT_SYMBOL(blk_quiesce_timeout);
> > +
> > /**
> > * blk_sync_queue - cancel any pending callbacks on a queue
> > * @q: the queue
> > @@ -408,8 +437,7 @@ EXPORT_SYMBOL(blk_stop_queue);
> > */
> > void blk_sync_queue(struct request_queue *q)
> > {
> > - del_timer_sync(&q->timeout);
> > - cancel_work_sync(&q->timeout_work);
> > + blk_quiesce_timeout(q);
> >
> > if (q->mq_ops) {
> > struct blk_mq_hw_ctx *hctx;
> > @@ -421,6 +449,8 @@ void blk_sync_queue(struct request_queue *q)
> > } else {
> > cancel_delayed_work_sync(&q->delay_work);
> > }
> > +
> > + __blk_unquiesce_timeout(q);
> > }
> > EXPORT_SYMBOL(blk_sync_queue);
> >
> > diff --git a/block/blk-mq.c b/block/blk-mq.c
> > index 0dc9e341c2a7..890dd3b3e3e1 100644
> > --- a/block/blk-mq.c
> > +++ b/block/blk-mq.c
> > @@ -901,6 +901,15 @@ static void blk_mq_timeout_work(struct work_struct *work)
> > };
> > struct blk_mq_hw_ctx *hctx;
> > int i;
> > + bool timeout_off;
> > + unsigned long flags;
> > +
> > + spin_lock_irqsave(q->queue_lock, flags);
> > + timeout_off = q->timeout_off;
> > + spin_unlock_irqrestore(q->queue_lock, flags);
> > +
> > + if (timeout_off)
> > + return;
>
> Looks like there is still race as following:
>
> blk_quiesce_timeout blk_mq_timeout_work
> -> timeout_off = q->timeout_off; //still a false
> -> q->timeout_off = true;
> -> del_timer_sync(&q->timeout);
> -> mod_timer
> -> cancel_work_sync(&q->timeout_work);
No, there isn't such race, the 'mod_timer' doesn't make a difference
because 'q->timeout_off' will be visible in new work func after
cancel_work_sync() returns. So even the timer is expired, work func
still returns immediately.
That means del_timer_sync() isn't absolutely necessary too.
Thanks,
Ming
next prev parent reply other threads:[~2018-05-02 3:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 15:41 [PATCH V2 0/5] nvme: pci: fix & improve timeout handling Ming Lei
2018-04-29 15:41 ` [PATCH V2 1/5] block: introduce blk_quiesce_timeout() and blk_unquiesce_timeout() Ming Lei
2018-05-02 2:23 ` jianchao.wang
2018-05-02 3:33 ` Ming Lei [this message]
2018-05-02 5:16 ` jianchao.wang
2018-04-29 15:41 ` [PATCH V2 2/5] nvme: pci: cover timeout for admin commands running in EH Ming Lei
2018-04-29 15:41 ` [PATCH V2 3/5] nvme: pci: only wait freezing if queue is frozen Ming Lei
2018-04-29 15:41 ` [PATCH V2 4/5] nvme: fix race between freeze queues and unfreeze queues Ming Lei
2018-04-29 15:41 ` [PATCH V2 5/5] nvme: pci: simplify timeout handling Ming Lei
2018-05-02 2:23 ` jianchao.wang
2018-05-02 4:54 ` Ming Lei
2018-05-02 5:12 ` jianchao.wang
2018-05-02 7:27 ` 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=20180502033342.GD22363@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=hch@lst.de \
--cc=jianchao.w.wang@oracle.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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