On Thu, Feb 09, 2006 at 12:39:20AM +0100, Stefan Richter wrote:
> Could the fact that Linux reboots (if sbp2 does not mangle the SCSI
> commands) mean that the SBP-2 target is overwriting memory outside of a
> data buffer? Or does the SCSI stack perform reckless things like jumps
> based on pointer tables, using unchecked data? Or...?
Interesting... What's the last command sent before reboot? Note that
original driver would remap 6byte commands to 10byte ones, but new one
should not _get_ those commands. At all. What happens if you take old
driver, put
sdev->use_10_for_rw = 1;
sdev->use_10_for_ms = 1;
into sbp2scsi_slave_configure() and leave remapping code alone? Then
see if remapper is ever triggered - if it does, we have a problem in
midlayer. If not... I'd love to see the last commands.
BTW, I've seen PL3507-based enclosure <spit> with the following lovely
bug: if it _ever_ got INQUIRY (any INQUIRY) other than immediately in
the beginning of session, it got 8 bytes stuck in FIFO. All subsequeunt
reads got shifted by 8 bytes, no matter what. With old driver, new driver...
Just scsiinfo -i would be enough to screw it. With massive fs corruption,
obviously...
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
