public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
	SCSI development list <linux-scsi@vger.kernel.org>,
	USB Storage List <usb-storage@one-eyed-alien.net>,
	Harald Dunkel <harri@synopsys.COM>
Subject: Re: Maximum_transfer_size and SCSI request buffer size parameters
Date: Thu, 24 Jul 2003 17:35:05 +0200	[thread overview]
Message-ID: <20030724153505.GC1063@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0307241035140.720-100000@ida.rowland.org>

On Thu, Jul 24 2003, Alan Stern wrote:
> I'm trying to solve the problem of a user whose USB disk drive crashes
> when it is asked to write 512K bytes in a single command.  A good way to
> solve this problem would be to have a maximum_transfer_size field as part 
> of the scsi_device structure.  Is it worthwhile adding such a feature?

First of all, you don't mention what kernel version you are talking
about...

Anyways, the feature is already there. It's called max_sectors, and it's
even in the host template for you to set. That handles block layer
requests, at least.

> In sd.c and sr.c, scmd->request_bufflen is the number of bytes to
> transfer.  Both files use the variable this_count to compute the number
> of sectors, stored in the command's CDB.  this_count is based on
> request_bufflen, but the values can disagree.  For example, if READ(6)  
> is used and request_bufflen corresponds to more than 255 sectors, 
> this_count will be reduced to 255.

That is in purpose, for cases like that you have to only do a part of
the entire request.

> Furthermore, sr.c goes to the trouble of adding up the lengths of all the
> scatter-gather blocks, and if the total disagrees with request_bufflen it
> sets request_bufflen equal to the total -- but it does this after storing
> this_count in the CDB.

It's a bug if they differ, that's why there's a printk there. Might be a
good idea to make that a harder error, though.

> A related issue is that in both sd.c and sr.c, the rw_intr() routine
> identifies the number of sectors correctly transferred as scmd->bufflen
> (if no error occurred).  Normally bufflen is initialized equal to
> request_bufflen.  But if this_count has been altered, the number of
> sectors will be different from bufflen.

The device will not transfer more data than what it is told from the
cdb. Aren't you getting a completed byte count from your hardware? Or
are you blindly assuming the device transferred what you initially told
you?

> If nobody objects, I will work on a patch to fix these problems.

Well..

-- 
Jens Axboe


  reply	other threads:[~2003-07-24 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 15:12 Maximum_transfer_size and SCSI request buffer size parameters Alan Stern
2003-07-24 15:35 ` Jens Axboe [this message]
2003-07-24 16:22   ` Alan Stern
2003-07-24 19:50   ` PATCH: (as70) " Alan Stern
2003-07-28 14:10   ` Retry scsi_mode_sense if UNIT ATTENTION occurs Alan Stern
2003-07-28 15:08     ` Jeff Garzik
2003-07-28 15:31       ` Alan Stern
2003-07-29 20:28     ` Kai Makisara
2003-07-29 21:10       ` Alan Stern
2003-07-29 23:23     ` James Bottomley
2003-07-30 14:09       ` Alan Stern
2003-07-30 19:10         ` Matthew Dharm

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=20030724153505.GC1063@suse.de \
    --to=axboe@suse.de \
    --cc=harri@synopsys.COM \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mdharm-usb@one-eyed-alien.net \
    --cc=stern@rowland.harvard.edu \
    --cc=usb-storage@one-eyed-alien.net \
    /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