From: Duncan Sands <duncan.sands@math.u-psud.fr>
To: Arjan van de Ven <arjan@infradead.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>,
chas@cmf.nrl.navy.mil
Subject: Re: possible recursive locking in ATM layer
Date: Wed, 5 Jul 2006 12:23:33 +0200 [thread overview]
Message-ID: <200607051223.34339.duncan.sands@math.u-psud.fr> (raw)
In-Reply-To: <1152029582.3109.70.camel@laptopd505.fenrus.org>
> ok this is a real potential deadlock in a way, it takes two locks of 2
> skbuffs without doing any kind of lock ordering; I think the following
> patch should fix it. Just sort the lock taking order by address of the
> skb.. it's not pretty but it's the best this can do in a minimally
> invasive way.
The patch is effective. Thanks for making it!
Best wishes,
Duncan.
next prev parent reply other threads:[~2006-07-05 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 15:59 possible recursive locking in ATM layer Duncan Sands
2006-07-04 16:13 ` Arjan van de Ven
2006-07-05 10:23 ` Duncan Sands [this message]
2006-07-05 13:33 ` Avi Kivity
2006-07-05 13:42 ` Arjan van de Ven
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=200607051223.34339.duncan.sands@math.u-psud.fr \
--to=duncan.sands@math.u-psud.fr \
--cc=arjan@infradead.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@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