All of lore.kernel.org
 help / color / mirror / Atom feed
From: chris hyser <chris.hyser@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH v3] sunvdc: Complete I/O request if vdisk server error
Date: Mon, 30 Mar 2015 17:05:46 +0000	[thread overview]
Message-ID: <5519826A.8080708@oracle.com> (raw)
In-Reply-To: <55197CB6.2020903@oracle.com>

If the underlying VDS driver error is not intermittent and callers ignore the error and keep issuing requests or the 
queue is filled, I suppose there could be a flood of messages.

On 3/30/2015 12:56 PM, David Ahern wrote:
> On 3/30/15 10:41 AM, chris hyser wrote:
>> diff --git a/drivers/block/sunvdc.c b/drivers/block/sunvdc.c
>> index 4b911ed..dad85fe 100644
>> --- a/drivers/block/sunvdc.c
>> +++ b/drivers/block/sunvdc.c
>> @@ -308,7 +308,11 @@ static void vdc_end_one(struct vdc_port *port,
>> struct vio_dring_state *dr,
>>
>>       rqe->req = NULL;
>>
>> -    __blk_end_request(req, (desc->status ? -EIO : 0), desc->size);
>> +    if (desc->status) {
>> +        pr_err(PFX "VIO I/O Error %d\n", desc->status);
>
> printk_ratelimit()? i.e., any chance these can come out in a flood?
>
>
>> +        __blk_end_request_all(req, -EIO);
>> +    } else
>> +        __blk_end_request(req, 0, desc->size);
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-03-30 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 16:41 [PATCH v3] sunvdc: Complete I/O request if vdisk server error chris hyser
2015-03-30 16:56 ` David Ahern
2015-03-30 17:05 ` chris hyser [this message]
2015-03-31 14:52 ` David Miller
2015-04-08  3:17 ` David Miller

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=5519826A.8080708@oracle.com \
    --to=chris.hyser@oracle.com \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.