public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
To: "Russell King" <rmk@arm.linux.org.uk>,
	"Mike Anderson" <andmike@us.ibm.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19 SCSI core bug?
Date: Thu, 12 Sep 2002 11:41:17 +0200	[thread overview]
Message-ID: <20020912094117.10936@192.168.4.1> (raw)
In-Reply-To: <20020912174530.B3121@flint.arm.linux.org.uk>

>1. we need to come up with a way of reasonably handing SCSI medium
>   errors if we are going to use the READ10 command with the FUA
>   bit clear.
>
>2. we could just set the FUA bit and bypass the drives on-board
>   cache completely.
>
>Note that the only reason I've found this is because my HBA drives
>are _really_ pedantic about checking that all expected data does
>in fact get transferred by the drive.
>
>I wonder how many other drives out there are buggy like this. 8/

What about setting FUA on the next command after an error ?

Would this work or may the disk really keep stale data around ?

I don't have a recent SCSI spec at hand, but is there a command
we can send after an error to force a cache flush & invalidate
or will it only flush dirty datas to platter and not invalidate ?

Ben.




      reply	other threads:[~2002-09-12 21:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 21:19 2.4.19 SCSI core bug? Russell King
2002-09-12  9:01 ` Russell King
2002-09-12 15:39   ` Mike Anderson
2002-09-12 15:42     ` Russell King
2002-09-12 16:45       ` Russell King
2002-09-12  9:41         ` Benjamin Herrenschmidt [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=20020912094117.10936@192.168.4.1 \
    --to=benh@kernel.crashing.org \
    --cc=andmike@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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