From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org, Stefan Weinhuber <wein@de.ibm.com>
Subject: Re: [PATCH 4/9] dasd: Implement block timeout handling
Date: Tue, 29 Jan 2013 12:32:28 +0100 [thread overview]
Message-ID: <20130129113228.GA5984@osiris> (raw)
In-Reply-To: <1359443521-24670-5-git-send-email-hare@suse.de>
On Tue, Jan 29, 2013 at 08:11:56AM +0100, Hannes Reinecke wrote:
> This patch implements generic block layer timeout handling
> callbacks for DASDs. When the timeout expires the respective
> cqr is aborted.
>
> With this timeout handler time-critical request abort
> is guaranteed as the abort does not depend on the internal
> state of the various DASD driver queues.
>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> Acked-by: Stefan Weinhuber <wein@de.ibm.com>
[...]
> +enum blk_eh_timer_return dasd_times_out(struct request *req)
> +{
> + struct dasd_ccw_req *cqr = req->completion_data;
> + struct dasd_block *block = req->q->queuedata;
> + struct dasd_device *device;
> + int rc = 0;
> +
> + if (!cqr)
> + return BLK_EH_NOT_HANDLED;
> +
> + device = cqr->startdev ? cqr->startdev : block->base;
> + DBF_DEV_EVENT(DBF_WARNING, device,
> + " dasd_times_out cqr %p status %x",
> + cqr, cqr->status);
> +
> + spin_lock(&block->queue_lock);
> + spin_lock(get_ccwdev_lock(device->cdev));
^^^
> + cqr->retries = -1;
> + cqr->intrc = -ETIMEDOUT;
> + if (cqr->status >= DASD_CQR_QUEUED) {
> + spin_unlock(get_ccwdev_lock(device->cdev));
> + rc = dasd_cancel_req(cqr);
> + } else if (cqr->status == DASD_CQR_FILLED ||
> + cqr->status == DASD_CQR_NEED_ERP) {
> + cqr->status = DASD_CQR_TERMINATED;
> + spin_unlock(get_ccwdev_lock(device->cdev));
> + } else if (cqr->status == DASD_CQR_IN_ERP) {
> + struct dasd_ccw_req *searchcqr, *nextcqr, *tmpcqr;
> +
> + list_for_each_entry_safe(searchcqr, nextcqr,
> + &block->ccw_queue, blocklist) {
> + tmpcqr = searchcqr;
> + while (tmpcqr->refers)
> + tmpcqr = tmpcqr->refers;
> + if (tmpcqr != cqr)
> + continue;
> + /* searchcqr is an ERP request for cqr */
> + searchcqr->retries = -1;
> + searchcqr->intrc = -ETIMEDOUT;
> + if (searchcqr->status >= DASD_CQR_QUEUED) {
> + spin_lock(get_ccwdev_lock(device->cdev));
^^^
This looks like a potential dead lock.
next prev parent reply other threads:[~2013-01-29 11:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 7:11 [PATCH 0/9] dasd: implement block timeout Hannes Reinecke
2013-01-29 7:11 ` [PATCH 1/9] dasd: Clarify comment Hannes Reinecke
2013-01-29 7:11 ` [PATCH 2/9] dasd: make number of retries configurable Hannes Reinecke
2013-01-29 7:11 ` [PATCH 3/9] dasd: process all requests in the device tasklet Hannes Reinecke
2013-01-29 7:11 ` [PATCH 4/9] dasd: Implement block timeout handling Hannes Reinecke
2013-01-29 11:32 ` Heiko Carstens [this message]
2013-01-29 11:34 ` Hannes Reinecke
2013-01-29 7:11 ` [PATCH 5/9] dasd: Reduce amount of messages for specific errors Hannes Reinecke
2013-01-29 7:11 ` [PATCH 6/9] dasd: detailed I/O errors Hannes Reinecke
2013-01-29 7:11 ` [PATCH 7/9] block: check for timeout function in blk_rq_timed_out() Hannes Reinecke
2013-01-29 7:12 ` [PATCH 8/9] dasd: Add 'timeout' attribute Hannes Reinecke
2013-01-29 11:36 ` Heiko Carstens
2013-01-29 11:41 ` Hannes Reinecke
2013-01-29 15:17 ` Stefan Weinhuber
2013-01-29 15:27 ` Hannes Reinecke
2013-01-29 7:12 ` [PATCH 9/9] dasd: Fail all requests when DASD_FLAG_ABORTIO is set Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2013-01-30 9:26 [PATCH 0/9][v2] dasd: implement block timeout Hannes Reinecke
2013-01-30 9:26 ` [PATCH 4/9] dasd: Implement block timeout handling Hannes Reinecke
2013-06-03 15:03 [PATCH 0/9] dasd: implement block timeout Martin Schwidefsky
2013-06-03 15:03 ` [PATCH 4/9] dasd: Implement block timeout handling Martin Schwidefsky
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=20130129113228.GA5984@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=wein@de.ibm.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;
as well as URLs for NNTP newsgroup(s).