public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: crazyrushstar@yahoo.com.tw
Cc: linux-scsi@vger.kernel.org
Subject: Re: Fwd: Re: scsi_scan_host will hang up my system!
Date: Wed, 04 Oct 2006 09:04:02 +0200	[thread overview]
Message-ID: <45235CE2.5080604@suse.de> (raw)
In-Reply-To: <20060920105845.48447.qmail@web18301.mail.tpe.yahoo.com>

crazyrushstar@yahoo.com.tw wrote:
> I am still reading scsi_mid_low_api.txt file.
> 
> Report my newly discovery.
> Trace to kernel code,function call to
> "blk_execute_rq(req->q, NULL, req, 1);" at scsi_lib.c
> It's too deep to trace.
> 
> This function not response to my driver so that insmod
> stuck.
> 
It looks as if you trigger a recursion in the block layer.
We've stumbled across this, too; it can happen if a driver returns
SCSI_MLQUEUE_HOST_BUSY errorneously. This can cause a really deep or
even infinite stack depth (as is triggers blk_requeue_request over and
over again).
Check for such a condition and make sure that it is _temporary_.
Otherwise use proper SCSI error codes (ie DID_NO_CONNECT) which do not
have this problem.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux Products GmbH		S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2006-10-04  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 10:58 Fwd: Re: scsi_scan_host will hang up my system! crazyrushstar
2006-10-04  7:04 ` Hannes Reinecke [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=45235CE2.5080604@suse.de \
    --to=hare@suse.de \
    --cc=crazyrushstar@yahoo.com.tw \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox