From: Jens Axboe <jens.axboe@oracle.com>
To: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
Cc: schilling@fokus.fraunhofer.de, linux-kernel@vger.kernel.org,
arjan@infradead.org
Subject: Re: SCSI over USB showstopper bug?
Date: Mon, 6 Nov 2006 17:07:31 +0100 [thread overview]
Message-ID: <20061106160731.GZ13555@kernel.dk> (raw)
In-Reply-To: <454f5c12.CD9M9/FtHNVm1oDq%Joerg.Schilling@fokus.fraunhofer.de>
On Mon, Nov 06 2006, Joerg Schilling wrote:
> Jens Axboe <jens.axboe@oracle.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
prev parent reply other threads:[~2006-11-06 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 22:08 SCSI over USB showstopper bug? Joerg Schilling
2006-10-31 22:18 ` Arjan van de Ven
2006-10-31 23:51 ` Joerg Schilling
2006-11-01 15:31 ` Jens Axboe
2006-11-01 18:25 ` Joerg Schilling
2006-11-01 18:31 ` Jens Axboe
2006-11-06 16:00 ` Joerg Schilling
2006-11-06 16:07 ` Jens Axboe [this message]
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=20061106160731.GZ13555@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Joerg.Schilling@fokus.fraunhofer.de \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schilling@fokus.fraunhofer.de \
/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