From: Mike Christie <michaelc@cs.wisc.edu>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Elric Fu <elricfu1@gmail.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
James Bottomley <JBottomley@Parallels.com>,
linux-scsi@vger.kernel.org,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Felipe Balbi <balbi@ti.com>, Alex He <alex.he@amd.com>,
Andiry Xu <andiry.xu@amd.com>,
Greg KH <gregkh@linuxfoundation.org>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: An oops will occur while SCSI core is being used in 3.4-rc1
Date: Tue, 10 Apr 2012 11:51:18 -0500 [thread overview]
Message-ID: <4F846506.4060801@cs.wisc.edu> (raw)
In-Reply-To: <4F846398.5030609@cs.wisc.edu>
On 04/10/2012 11:45 AM, Mike Christie wrote:
> On 04/10/2012 11:37 AM, Mike Christie wrote:
>> On 04/10/2012 03:16 AM, Bart Van Assche wrote:
>>> On 04/10/12 01:22, Elric Fu wrote:
>>>
>>>> After debugging the code, I found the issue happened while the driver ran to
>>>> line 782 in scsi_send_eh_cmnd().
>>>>
>>>> 778 static int scsi_send_eh_cmnd(struct scsi_cmnd *scmd, unsigned char *cmnd,
>>>> 779 int cmnd_size, int timeout, unsigned
>>>> sense_bytes)
>>>> 780 {
>>>> 781 struct scsi_device *sdev = scmd->device;
>>>> 782 struct scsi_driver *sdrv = scsi_cmd_to_driver(scmd);
>>>> 783 struct Scsi_Host *shost = sdev->host;
>>>> 784 DECLARE_COMPLETION_ONSTACK(done);
>>>> 785 unsigned long timeleft;
>>>> 786 struct scsi_eh_save ses;
>>>> 787 int rtn;
>>>>
>>>> I know the code is submitted by you. I don't familiar with the scsi core.
>>>> It seems like the conversion process from scsi command to scsi driver
>>>> encounter a NULL pointer. Any idea?
>>>
>>>
>>> I have observed crashes at the same point while testing device removal
>>> with the ib_srp driver. As far as I can see that code was added through
>>> commit 18a4d0a22ed6c54b67af7718c305cd010f09ddf8 (February 9, 2012). The
>>> approach of that patch looks questionable to me: what guarantees that
>>> the struct scsi_driver will be available at the time the SCSI error
>>> handler needs it ?
>>
>> If a scsi scan IO timesout then the driver will not be set yet. It is ok
>> to use scsi_cmd_to_driver in scsi_finish_cmd because of the req block pc
>> check (scsi scan IO set that flag and so do not hit that path).
>
> I meant to say that all REQ_TYPE_BLOCK_PC will have a NULL driver, so at
That is wrong. I guess REQ_DISCARD and REQ_FLUSH will, so I guess we
just have to check for a NULL sdrv above.
> the very least there should be a check in scsi_send_eh_cmnd for NULL
> sdrv or for the IO being a REQ_TYPE_BLOCK_PC like is done in
> scsi_finish_command.
next prev parent reply other threads:[~2012-04-10 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 1:22 An oops will occur while SCSI core is being used in 3.4-rc1 Elric Fu
2012-04-10 8:16 ` Bart Van Assche
2012-04-10 16:37 ` Mike Christie
[not found] ` <4F8461E3.3050808-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
2012-04-10 16:45 ` Mike Christie
2012-04-10 16:51 ` Mike Christie [this message]
2012-04-11 16:10 ` Martin K. Petersen
2012-04-11 16:40 ` Bart Van Assche
[not found] ` <4F85B3E8.7040704-HInyCGIudOg@public.gmane.org>
2012-04-11 20:01 ` Bart Van Assche
[not found] ` <4F85E312.6070205-HInyCGIudOg@public.gmane.org>
2012-04-12 0:48 ` Martin K. Petersen
2012-04-18 7:53 ` James Bottomley
2012-04-13 0:30 ` Rustad, Mark D
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=4F846506.4060801@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=JBottomley@Parallels.com \
--cc=alex.he@amd.com \
--cc=andiry.xu@amd.com \
--cc=balbi@ti.com \
--cc=bvanassche@acm.org \
--cc=elricfu1@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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.