linux-kernel - Re: sg timeout problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090506103852.19cb69b9@lxorguk.ukuu.org.uk>
Date:	Wed, 6 May 2009 10:38:52 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Norman Diamond" <n0diamond@...oo.co.jp>
Cc:	<linux-kernel@...r.kernel.org>, <linux-scsi@...r.kernel.org>
Subject: Re: sg timeout problem

> But if sg is running on top of an actual SCSI driver, someone aborts the
> ioctl after 3 seconds.  The ioctl returns success even though the operation
> didn't complete.  I tried this with two Adaptec drivers and one NinjaSCSI 
> driver with 100% repro.
> 
> What am I missing?  I need the call to run to completion. 

If you set it to the max of a signed int does it behave, or to a large
value thats well under the limit. That will help tell if there is a
problem with sign handling in the scsi code somewhere or it is getting
multiplied up for some reason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/