diff options
author | James Bottomley <James.Bottomley@suse.de> | 2010-05-04 16:51:40 -0400 |
---|---|---|
committer | James Bottomley <James.Bottomley@suse.de> | 2010-05-05 12:15:57 -0400 |
commit | 77a4229719e511a0d38d9c355317ae1469adeb54 (patch) | |
tree | 6547272402fca49cde94fd5cb7842eea08b45dd7 /mm/migrate.c | |
parent | c213e1407be6b04b144794399a91472e0ef92aec (diff) | |
download | kernel_samsung_tuna-77a4229719e511a0d38d9c355317ae1469adeb54.zip kernel_samsung_tuna-77a4229719e511a0d38d9c355317ae1469adeb54.tar.gz kernel_samsung_tuna-77a4229719e511a0d38d9c355317ae1469adeb54.tar.bz2 |
[SCSI] Retry commands with UNIT_ATTENTION sense codes to fix ext3/ext4 I/O error
There's nastyness in the way we currently handle barriers (and
discards): They're effectively filesystem commands, but they get
processed as BLOCK_PC commands. Unfortunately BLOCK_PC commands are
taken by SCSI to be SG_IO commands and the issuer expects to see and
handle any returned errors, however trivial. This leads to a huge
problem, because the block layer doesn't expect this to happen and any
trivially retryable error on a barrier causes an immediate I/O error
to the filesystem.
The only real way to hack around this is to take the usual class of
offending errors (unit attentions) and make them all retryable in the
case of a REQ_HARDBARRIER. A correct fix would involve a rework of
the entire block and SCSI submit system, and so is out of scope for a
quick fix.
Cc: Hannes Reinecke <hare@suse.de>
Cc: Stable Tree <stable@kernel.org>
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'mm/migrate.c')
0 files changed, 0 insertions, 0 deletions