From: Jens Axboe <axboe@suse.de>
To: Kernel Developer List <linux-kernel@vger.kernel.org>,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: error in drivers/block/scsi_ioctl.c and ll_rw_block.c?
Date: Mon, 29 Sep 2003 09:55:46 +0200 [thread overview]
Message-ID: <20030929075546.GP15415@suse.de> (raw)
In-Reply-To: <20030929075105.GO15415@suse.de>
On Mon, Sep 29 2003, Jens Axboe wrote:
> On Sun, Sep 28 2003, Matthew Dharm wrote:
> > While working on usb-storage (a virtual SCSI HBA), I noticed that the
> > command 'eject /dev/scd0' sent a START_STOP command to the device with the
> > data direction set to SCSI_DATA_WRITE but a transfer length of zero. This
> > causes a problem for some code paths.
> >
> > For clarity, the START_STOP command doesn't want to move any data at all.
> >
> > It looks to me like the error is a combination of
> > drivers/block/scsi_ioctl.c and ll_rw_block.c
> >
> > scsi_ioctl.c calls blk_get_request(q, WRITE, __GFP_WAIT) to allocate the
> > request -- specifying WRITE here is one problem.
> >
> > In ll_rw_block.c, blk_get_request() calls BUG_ON(rq != READ && rw != WRITE)
> > -- in other words, it can only allocate a request for reading or writing,
> > but not for no data. I'm not familiar with this code, but it looks like
> > requests are tracked by data direction, so making this accept NONE may be
> > difficult.
> >
> > One possible solution may be to re-write the CDROMEJECT ioctl into a call
> > to sg_scsi_ioctl(), but that doesn't fix the general problem with
> > ll_rw_block.c -- if, indeed, that is a problem.
>
> No it's not a problem, clearly the request doesn't want to move any data
> if rq->data_len == 0.
This one compiles :)
===== drivers/scsi/sr.c 1.93 vs edited =====
--- 1.93/drivers/scsi/sr.c Fri Sep 5 13:31:51 2003
+++ edited/drivers/scsi/sr.c Mon Sep 29 09:55:19 2003
@@ -289,12 +289,12 @@
return 0;
memcpy(SCpnt->cmnd, rq->cmd, sizeof(SCpnt->cmnd));
- if (rq_data_dir(rq) == WRITE)
+ if (!rq->data_len)
+ SCpnt->sc_data_direction = SCSI_DATA_NONE;
+ else if (rq_data_dir(rq) == WRITE)
SCpnt->sc_data_direction = SCSI_DATA_WRITE;
- else if (rq->data_len)
- SCpnt->sc_data_direction = SCSI_DATA_READ;
else
- SCpnt->sc_data_direction = SCSI_DATA_NONE;
+ SCpnt->sc_data_direction = SCSI_DATA_READ;
this_count = rq->data_len;
if (rq->timeout)
--
Jens Axboe
prev parent reply other threads:[~2003-09-29 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 23:02 error in drivers/block/scsi_ioctl.c and ll_rw_block.c? Matthew Dharm
2003-09-29 7:51 ` Jens Axboe
2003-09-29 7:55 ` 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=20030929075546.GP15415@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.