All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian King <brking@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Olaf Hering <olh@suse.de>, linux-scsi@vger.kernel.org
Subject: Re: 2.6.16-rc1 crash in scsi_target_reap_work
Date: Fri, 10 Feb 2006 15:28:58 -0600	[thread overview]
Message-ID: <43ED059A.1080509@us.ibm.com> (raw)
In-Reply-To: <1139580295.3084.3.camel@mulgrave.il.steeleye.com>

James Bottomley wrote:
> On Fri, 2006-02-10 at 11:11 +0100, Olaf Hering wrote:
>>550 reboots without crash, with this patch reverted.
>>Will try the execute_in_process_context thing now.
> 
> I wouldn't bother ... because of the structure, the
> execute_in_process_context() patch must have the same bug, but the
> context check will make it much more difficult to hit.
> 
> Go back to the original and see if you can diagnose what is NULL and
> why.  The target is supposed to have a reference on the parent, so what
> was the parent in this case?  If it's a host, there's nothing I can
> think of that can produce the behaviour you see; if it's something else,
> like an rport or phy then we may have a transport class issue.

Taking a quick look at the scsi_target_reap_work patch that went in,
one of the things it changed in this regard was the fact that the
caller of scsi_target_reap always has a ref to the starget->dev, which
would have protected scsi_target_reap from ever releasing the
starget->dev. Since the actual remove work was moved to a workqueue,
the get and put that the callers of scsi_target_reap are doing is no longer
adding the same protection it was before.


-- 
Brian King
eServer Storage I/O
IBM Linux Technology Center

  parent reply	other threads:[~2006-02-10 21:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17  0:05 2.6.15-git12, slab corruption in ipr Olaf Hering
2006-01-18 18:42 ` Brian King
2006-01-19 21:05   ` Olaf Hering
2006-01-30 10:46     ` Olaf Hering
2006-01-30 16:49       ` Olaf Hering
2006-02-06 22:04         ` 2.6.16-rc1 crash in scsi_target_reap_work Olaf Hering
2006-02-06 22:26           ` Olaf Hering
2006-02-06 22:44           ` James Bottomley
2006-02-09 20:05             ` Olaf Hering
2006-02-10 10:11               ` Olaf Hering
2006-02-10 14:04                 ` James Bottomley
2006-02-10 14:10                   ` Olaf Hering
2006-02-10 23:01                     ` Olaf Hering
2006-02-10 23:21                       ` Brian King
2006-02-10 23:29                         ` Olaf Hering
2006-02-11 10:34                           ` Olaf Hering
2006-02-20 23:00                           ` Brian King
2006-02-22  8:36                             ` Olaf Hering
2006-02-22 14:38                               ` Brian King
2006-02-22 15:53                                 ` Olaf Hering
2006-02-22 16:47                                 ` Mike Anderson
2006-02-22 17:05                                   ` James Bottomley
2006-02-10 21:28                   ` Brian King [this message]
2006-01-30 18:07 ` 2.6.15-git12, slab corruption in ipr Olaf Hering

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=43ED059A.1080509@us.ibm.com \
    --to=brking@us.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olh@suse.de \
    /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.