From: Hannes Reinecke <hare@suse.de>
To: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
Cc: James Bottomley <jbottomley@parallels.com>,
linux-scsi@vger.kernel.org, Dave Chinner <david@fromorbit.com>,
Ren Mingxin <renmx@cn.fujitsu.com>, Theodore Tso <tytso@mit.edu>,
linux-fsdevel@vger.kernel.org,
device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 4/5] scsi: Return ENODATA on medium error
Date: Mon, 01 Jul 2013 11:51:55 +0200 [thread overview]
Message-ID: <51D1513B.1030908@suse.de> (raw)
In-Reply-To: <51D14813.6070803@ce.jp.nec.com>
On 07/01/2013 11:12 AM, Jun'ichi Nomura wrote:
> On 07/01/13 17:12, Hannes Reinecke wrote:
>> When a medium error is detected the SCSI stack should return
>> ENODATA to the upper layers.
>
> Hi Hannes,
>
> since you change the error code from -EREMOTEIO to -ENODATA/-ENOSPC,
> upper layers that checks -EREMOTEIO have to be updated as well.
>
> Something like below for dm-multipath.
> It seems btrfs checking -EREMOTEIO, too.
>
Good point.
Will be updating the patchset.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-07-01 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1372666331-66996-1-git-send-email-hare@suse.de>
[not found] ` <1372666331-66996-5-git-send-email-hare@suse.de>
2013-07-01 9:12 ` [PATCH 4/5] scsi: Return ENODATA on medium error Jun'ichi Nomura
2013-07-01 9:51 ` Hannes Reinecke [this message]
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=51D1513B.1030908@suse.de \
--to=hare@suse.de \
--cc=david@fromorbit.com \
--cc=dm-devel@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=jbottomley@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=renmx@cn.fujitsu.com \
--cc=tytso@mit.edu \
/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