All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: giridhar.malavali@qlogic.com, bharrosh@panasas.com,
	linux-scsi@vger.kernel.org, James.Smart@Emulex.Com
Subject: Re: kernel crash when BSG request timesout
Date: Thu, 28 May 2009 09:54:28 -0400	[thread overview]
Message-ID: <4A1E9794.7090503@interlog.com> (raw)
In-Reply-To: <20090528150147U.fujita.tomonori@lab.ntt.co.jp>

FUJITA Tomonori wrote:
> CC'ed James Smart,
> 
> On Tue, 26 May 2009 11:38:14 -0700
> Giridhar Malavali <giridhar.malavali@qlogic.com> wrote:
> 
>> Thanks for the pointer. I will check with the post-merge tree.
>>
>> 	The crash I am seeing is because of softirq_done_fn not set in the  
>> request queue for BSG request. Even in the post-merge tree I don't see  
>> FC transport setting this function during the allocation of the  
>> request queue.  When BSG request times out, I see that it executes  
>> __blk_complete_request function where check is done for its existence.  
>> I see this getting set for SCSI request during queue allocation in  
>> scsi_lib.c. Is this required for BSG request?
> 
> Yeah, you need to set q->softirq_done_fn if you use the block timeout
> infrastructure. The current bsg user, SMP, uses bsg but it doesn't use
> the timeout infrastructure so it doesn't set q->softirq_done_fn.

sg3_utils version 1.27 (and later) is a user of bsg, sending
SCSI commands through. Will timeouts works? [I didn't check.]

Doug Gilbert

  parent reply	other threads:[~2009-05-28 13:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 20:51 kernel crash when BSG request timesout Giridhar Malavali
2009-05-24 11:00 ` Boaz Harrosh
2009-05-26 18:38   ` Giridhar Malavali
2009-05-28  6:01     ` FUJITA Tomonori
2009-05-28  6:12       ` FUJITA Tomonori
2009-06-10  7:56         ` [Suspected SPAM] " Giridhar Malavali
2009-06-10  8:40           ` FUJITA Tomonori
2009-05-28 13:54       ` Douglas Gilbert [this message]
2009-05-28 22:23         ` FUJITA Tomonori

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=4A1E9794.7090503@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=James.Smart@Emulex.Com \
    --cc=bharrosh@panasas.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=giridhar.malavali@qlogic.com \
    --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.