From: Pat LaVarre <p.lavarre@ieee.org>
To: Jens Axboe <axboe@suse.de>
Cc: dougg@torque.net, linux-scsi@vger.kernel.org
Subject: Re: sense visible despite ide-floppy in 2.6 maybe
Date: 09 Jun 2004 12:51:23 -0600 [thread overview]
Message-ID: <1086807083.3741.21.camel@patibmrh9> (raw)
In-Reply-To: <1086805796.3741.5.camel@patibmrh9>
> Also something's broken (far far outside of the kernel) in plscsi. I
> found success only by patching the trivial sgio.c that I posted in this
> thread, as shown below.
Ah. That is, despite the patch inserting idefloppy_blockpc_cmd,
ioctl(fd, SG_GET_VERSION_NUM, &vn) returns negative.
Pat LaVarre
P.S. More specifically,
plscsi, with perhaps excessively paranoid automagic, therefore chose not
to try 2.4 style ioctl SG_IO, complaining:
// sgioOpen.ioctl: Invalid argument
// plscsi.sclOpenNext: "/dev/hdd" not opened
By contrast, my back-of-the-envelope sgio.c was quietly stepping past
this trouble without complaint, in fact requiring vn at or beyond 30,000
only from devices that do support ioctl fd SG_GET_VERSION &vn. The
trivial patch to get that fragment of code to behave as sensitively as
plscsi is of course:
--- sgio.was.c 2004-06-08 09:33:33.000000000 -0600
+++ sgio.c 2004-06-09 12:43:16.899046392 -0600
@@ -61,12 +61,15 @@ int main(int argc, char * argv[])
--argc; ++argv;
for (ix = 0; ix < argc; ++ix)
{
- int fd = open(argv[ix], O_NONBLOCK|O_RDWR);
+ int fd = open(argv[ix], O_NONBLOCK);
if (fd < 0) {
perror("open");
} else {
int vn = 0;
- if (0 <= ioctl(fd, SG_GET_VERSION_NUM, &vn)) {
+ if (ioctl(fd, SG_GET_VERSION_NUM, &vn) < 0) {
+ perror("ioctl SG_GET_VERSION_NUM");
+ ; /* fallthru to talk anyhow */
+ } else {
if (vn < 30000) {
perror("ioctl SG_GET_VERSION_NUM");
continue;
next prev parent reply other threads:[~2004-06-09 18:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 15:53 sense visible despite ide-floppy in 2.6 maybe Pat LaVarre
2004-06-09 8:00 ` Jens Axboe
2004-06-09 8:20 ` Jens Axboe
2004-06-09 16:22 ` Pat LaVarre
2004-06-09 17:37 ` Jens Axboe
2004-06-09 18:29 ` Pat LaVarre
2004-06-09 18:51 ` Pat LaVarre [this message]
2004-06-09 23:30 ` Pat LaVarre
2004-06-11 9:30 ` Jens Axboe
2004-06-11 9:38 ` Jens Axboe
2004-06-13 18:48 ` Pat LaVarre
2004-06-13 19:58 ` Jens Axboe
2004-06-11 9:24 ` Jens Axboe
2004-06-11 9:24 ` Jens Axboe
2004-06-11 0:23 ` Douglas Gilbert
2004-06-11 2:08 ` Willem Riede
2004-06-13 18:21 ` Pat LaVarre
2004-06-13 19:06 ` Pat LaVarre
2004-06-14 6:39 ` Douglas Gilbert
2004-06-13 20:00 ` Jens Axboe
2004-06-17 19:03 ` Pat LaVarre
2004-06-17 19:12 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1086807083.3741.21.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=axboe@suse.de \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox