Meelis Roos wrote: >>> It outputs random data from memory as a response to the scsi command, >>> different recent strings different times. >> >> >> This is a bug in blktool, so please refile appropriately. > > > Yes, I see. blktools seems to buggy, yes. May I suggest that you try sdparm for SCSI devices until blktool is fixed. > But blktool outputs memory fragments that seems to come from other > processes. I saw string "bash", "lled with unallocated bl" and other > strings that do not appear in blktools image. Without further > investigation it seems that in case of the error, soma data ise leaked > from kernel to the buggy program in userspace (blktool in this case). After analysing the blktool code (4.2), and having a similar worrying report concerning sdparm, what you may have seen was the uninitialized contents of a auto variable (buf[128]) in blktool. As James B. pointed out, the failure in the aic7xxx driver was due to an INQUIRY command issued with a cdb length set to 12 bytes (it should be 6). Given that failure there should have been no DMA from the device back to the kernel memory. If kernel memory was still moved back to the user space then that is an issue. The sg driver zeroes its kernel buffers for all non-root users before data is moved through them as a safeguard. There can also be "short" DMA transfer back from a device, indicated by resid>0 that should be considered in this context. Doug Gilbert - : 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
