From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH 7/8] don't mangle INQUIRY if cmddt or evpd bits are set
Date: Tue, 14 Feb 2006 09:37:35 +0100 [thread overview]
Message-ID: <43F196CF.9060608@s5r6.in-berlin.de> (raw)
In-Reply-To: <20060214024049.GB27946@ftp.linux.org.uk>
Al Viro wrote:
> On Mon, Feb 13, 2006 at 09:28:17PM +0100, Stefan Richter wrote:
...
>> - The TI StorageLynx based bridge reports device type 0 (TYPE_DISK).
>> The problem occurs apparently with page 4 and page 8. Sbp2 has a
>> fix since yesterday which sets the skip_ms_page_8 flag.
>
> That's going to cause fun problems on reboot if it actually has write-behind
> cache...
Not only on reboot but always when sd is told to shut down. I did not
notice an actual problem so far but I will keep an eye on it.
But AFAIU, sd's cache syncing (of devices with WCE set) is ineffective
anyway if devices are unplugged without manually shutting the driver
down beforehand.
>> http://marc.theaimsgroup.com/?l=linux1394-devel&m=113969287630893
>> - Another bridge made by the same manufacturer but based on TI
>> StorageLynx revision A features the same MODE SENSE bug. This bridge
>> reports type 14 (TYPE_RBC).
>
> Pardon? If it's type 14, we won't issue MODE SENSE for page 8 and will
> go for page 6 instead...
Correct. Which is why I did not notice the bug until testing with scsiinfo.
...
>>Of course sg does not care for any black list flags (like sd_mod and
>>sr_mod do), but considering the nature of the bugs and anticipated usage
>>of affected devices, there is hardly a reason for further safeguards in
>>sbp2, let alone sg.
>
> Maybe, maybe not. Note that e.g. aforementioned INQUIRY bug in pl3507 is
> triggered by dmraid, which works via SG_IO, just as scsiinfo. And unlike
> scsiinfo it's run from /etc/rc.sysinit on current FC4...
Are they probing all devices or only those which are part of a RAID set?
--
Stefan Richter
-=====-=-==- --=- -===-
http://arcgraph.de/sr/
prev parent reply other threads:[~2006-02-14 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 20:31 Al Viro
2006-02-08 22:35 ` Stefan Richter
2006-02-08 23:05 ` Al Viro
2006-02-08 23:51 ` Stefan Richter
2006-02-13 16:19 ` Stefan Richter
2006-02-13 17:03 ` Jody McIntyre
2006-02-13 18:18 ` Al Viro
2006-02-13 20:28 ` Stefan Richter
2006-02-14 2:40 ` Al Viro
2006-02-14 8:37 ` Stefan Richter [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=43F196CF.9060608@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=viro@ftp.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
Powered by JetHome