linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <BB8F41726E2941CEB399F732BB3ED9E5@DIAMOND8600>
Date:	Wed, 6 May 2009 16:15:45 +0900
From:	"Norman Diamond" <n0diamond@...oo.co.jp>
To:	<linux-kernel@...r.kernel.org>, <linux-scsi@...r.kernel.org>
Subject: sg timeout problem

struct sg_io_hdr sg_io;
[...]
sg_io.timeout = UINT_MAX;
[...]
ioctl(fd, SG_IO, &sg_io);

As far as I can tell, if sg is running on top of LIBATA, the infinite
timeout is honoured.

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. 

--------------------------------------
Power up the Internet with Yahoo! Toolbar.
http://pr.mail.yahoo.co.jp/toolbar/
--
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/