From: Michael Reed <mdr@sgi.com>
To: linux-scsi <linux-scsi@vger.kernel.org>
Cc: Jeremy Higdon <jeremy@sgi.com>, Michael Reed <mdr@sgi.com>,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: REGRESSION: 2.6.20-rc3-git4: EIO not returned to direct i/o application following disk error
Date: Fri, 05 Jan 2007 15:05:55 -0600 [thread overview]
Message-ID: <459EBDB3.3080408@sgi.com> (raw)
Testing using 2.6.20-rc3-git4 I observed that my direct i/o test
application no longer receives an EIO when the fc transport deletes
a target following a fibre channel switch port disable.
With 2.6.19 EIO is returned and the application terminates.
With 2.6.20, the requested read length is returned with incorrect
data in the buffer.
(I was playing around with an error recovery patch when I first
discovered this, and do believe it is not limited in scope to
targets being removed by the transport.)
This is a serious regression which puts customer data at risk.
(Is there a formal mechanism for filing a bug?)
Mike
next reply other threads:[~2007-01-05 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 21:05 Michael Reed [this message]
2007-01-09 23:05 ` REGRESSION: 2.6.20-rc3-git4: EIO not returned to direct i/o application following disk error Michael Reed
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=459EBDB3.3080408@sgi.com \
--to=mdr@sgi.com \
--cc=James.Bottomley@SteelEye.com \
--cc=jeremy@sgi.com \
--cc=linux-scsi@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.