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] [day] [month] [year] [list]
Message-ID: <20061106160731.GZ13555@kernel.dk>
Date:	Mon, 6 Nov 2006 17:07:31 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Joerg Schilling <Joerg.Schilling@...us.fraunhofer.de>
Cc:	schilling@...us.fraunhofer.de, linux-kernel@...r.kernel.org,
	arjan@...radead.org
Subject: Re: SCSI over USB showstopper bug?

On Mon, Nov 06 2006, Joerg Schilling wrote:
> Jens Axboe <jens.axboe@...cle.com> wrote:
> 
> > > Then someone should change the source to match this statements.
> > > 
> > > From a report I have from the k3b Author, readcd and cdda2wav only work
> > > if you add a "ts=128k" option. 
> >
> > Then please file (or have him/her file) a proper bug report. It may be a
> > usb specific bug, or it may just be something else.
> 
> To me, it looks like a problem that happens with usb because there is 
> no proper interaction with SG_?ET_RESETVED_SIZE and the usb layer.

The limits are communicated from the usb layer to the block layer via
the SCSI layer, by setting proper limits in the scsi host adapter
template. SCSI then informs the block layer, by setting the appropriate
limits on the queue. Perhaps there's a usb-storage bug there, who knows,
so far there's been no real info posted.

> I am still in hope that someone will fix this soon.

Someone may very well fix it, but the odds of that happening when a real
bug report exists is a lot bigger. Who reported this issue to you? Get
him/her to file a proper bug report, as I wrote in my last mail as well.

-- 
Jens Axboe

-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ