From: "Andreas Herrmann" <andreas.herrmann3@amd.com>
To: Swen Schillig <swen.schillig@freenet.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] zfcp: Invalid locking order
Date: Wed, 7 Feb 2007 17:06:43 +0100 [thread overview]
Message-ID: <20070207160643.GE30311@alberich.amd.com> (raw)
In-Reply-To: <200702071317.58026.swen.schillig@freenet.de>
On Wed, Feb 07, 2007 at 01:17:57PM +0100, Swen Schillig wrote:
> From: Swen Schillig <swen@vnet.ibm.com>
>
> Invalid locking order. Kernel hangs after trying to take two locks
> which are dependend on each other. Introducing temporary variable
> to free requests. Free lock after requests are copied.
>
I am just curious. You didn't mention which locks are causing the dead
lock.
I've glanced through the code and it seems that locking order
of abort_lock and req_list_lock for adapters is inconsistent.
Is that the bug you try to fix?
Regards,
Andreas
next prev parent reply other threads:[~2007-02-07 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 12:17 [PATCH] zfcp: Invalid locking order Swen Schillig
2007-02-07 16:06 ` Andreas Herrmann [this message]
2007-02-07 16:19 ` Swen Schillig
2007-02-08 14:40 ` Heiko Carstens
2007-02-08 16:18 ` Andreas Herrmann
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=20070207160643.GE30311@alberich.amd.com \
--to=andreas.herrmann3@amd.com \
--cc=linux-scsi@vger.kernel.org \
--cc=swen.schillig@freenet.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.