--CE+1k2dSO48ffgeK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 17, 2005 at 06:42:08PM -0500, Michael Lorenz wrote:
> Hello,
>=20
> > > I'm not sure how far we should trust it - my gut feeling says this
> > > will expose other problems. In my opinion it should be mentioned
> > > but let's not rush anywhere without some thorough testing, after all
> > > this isn't really a lifesaver. Mesh without it works more or less,
> > > quirks and workarounds are pretty well known. With it - who knows.
> > > Works for   me but
> > > that doesn't mean anything.

While I agree with your caution, I don't think that starting to correctly=
=20
handle SCSI status will cause more problems than not. It make make more=20
problems visible than not, but I think that's a matter of visibility, not=
=20
reality.

It's too late for 3.0, but this change certainly should go into 3.1, and=20
3.0.x there after. And be noted.

> > It's a pretty obvious and serious bug -- no SCSI status is ever =20
> > returned without the fix (or random garbage).  It should be pulled up.
>=20
> You're the expert.
> So I'll request pullup 'approved by thorpej' ?

Should be fine. Just send the request. :-)

Take care,

Bill

--CE+1k2dSO48ffgeK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD4DBQFDpNjQWz+3JHUci9cRAlgbAJ0emD33SOGJ6sltrFHE89/jzcDiXACWJcPE
tMtdQFYGtcbUXl48pS7umg==
=HDy2
-----END PGP SIGNATURE-----

--CE+1k2dSO48ffgeK--