Re: How to detect if a libata ioctl SG_IO had an error?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I wrote:

> Now for today's discovery.
> 
> When the SG_IO ioctl times out, libata sets the ABRT bit but not the ERR bit in the sense data.  I was checking the ERR bit which was 0, and then going off on a wild goose chase trying to find what level SCSI driver reported the timeout error.  There was none.  It's all in the ABRT bit.  This looks like a bug in libata.

Wrong.  When the SG_IO ioctl times out, a lot of random values are still useless, and I'm still going off on wild goose chases.

How can the caller of ioctl detect if an error occured, where error includes timeout as well as other kinds of errors?
--
To unsubscribe from this list: 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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux