linux-kernel - Re: SCSI over USB showstopper bug?

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]

Date:	Wed, 01 Nov 2006 00:51:00 +0100
From:	Joerg.Schilling@...us.fraunhofer.de (Joerg Schilling)
To:	arjan@...radead.org
Cc:	schilling@...us.fraunhofer.de, linux-kernel@...r.kernel.org
Subject: Re: SCSI over USB showstopper bug?

Arjan van de Ven <arjan@...radead.org> wrote:

> On Tue, 2006-10-31 at 23:08 +0100, Joerg Schilling wrote:
> > Hi,
> > 
> > it looks as if SG_GET_RESERVED_SIZE & SG_SET_RESERVED_SIZE
> > are not in interaction with the underlying SCSI transport.
> > 
> > Programs like readcd and cdda2wav that try to get very large SCSI
> > transfer buffers get a confirmation for nearly any SCSI transfer size 
> > but later when readcd/cdda2wav try to transfer data with an
> > actual SCSI command, they fail with ENOMEM.
> > 
> > Correct fix: let sg.c make a callback to the underlying SCSI transport
> > 		and let it get a confirmation tfor the buffer size.
> > 
> > Quick and dirty fix: reduce the maximum allowed DMA size to the smallest
> > 		max DMA size of all SCSI transports.
>
> real good fix:
>
> use SG_IO on the device directly that checks this already

>From looking into the source, this claim seems to be wrong.

Jörg

-- 
 EMail:joerg@...ily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@...tu-berlin.de                (uni)  
       schilling@...us.fraunhofer.de     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
-
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/