Re: [usb-storage] mode sense blacklist how

[Pat LaVarre <p.lavarre@ieee.org>]

> > > The only really important question IMHO is
> > > how come SG_IO is not interruptible.
> >
> > Yes, now being pursued by Doug G in this thread.
>
> block/scsi_ioctl.c...
> I suspect ... cannot interrupt the sg_io... blk_do_rq...
> Perhaps someone could enlighten me (and I could document it).
>
> Further it looks like the SCSI_IOCTL_SEND_COMMAND is not
> interruptible either. See scsi_wait_req() in scsi_lib.c .

Open question I see.

> Apologies in advance for each reboot these experiments force on you.
> ...
> sg.c .... coping with orphaned SCSI responses from user killed
> processes requires a lot of logic ...

Ouch.

Designing an lk 2.6 user app to recommend more prominent devie names
like /dev/hdd and /dev/scd0 in place of less prominent /dev/sg$n names
thereby steers people into using the less robust pass thru of SG_IO via
block/scsi_ioctl.c.

> I suspect ... cannot interrupt ...

Sorry I'm too much of a kernelnewbie to guess confidently the full
implications of "not interruptible".  Does "not interruptible" mean
timeouts don't work, or does "not interruptible" mean that only timeouts
work, or does "not interruptible" mean that only timeouts and resets but
not SIGINT of the calling process works ...

I will return here with answers if I find them faster than people here
give them to me.

Pat LaVarre

P.S. Another open netiquette question is when we rename this thread.