From: "David S. Miller" <davem@davemloft.net>
To: spereira@tusc.com.au
Cc: akpm@osdl.org, netdev@vger.kernel.org, eis@baty.hanse.de,
linux-x25@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1]x25: fix for spinlock recurse and spinlock lockup with timer handler in x25
Date: Fri, 28 Apr 2006 12:00:33 -0700 (PDT) [thread overview]
Message-ID: <20060428.120033.86347954.davem@davemloft.net> (raw)
In-Reply-To: <1145509403.16180.10.camel@spereira05.tusc.com.au>
From: Shaun Pereira <spereira@tusc.com.au>
Date: Thu, 20 Apr 2006 15:03:23 +1000
> From: spereira@tusc.com.au
>
> When the sk_timer function x25_heartbeat_expiry() is called by the kernel
> in a running/terminating process, spinlock-recursion and spinlock-lockup
> locks up the kernel.
> This has happened with testing on some distro's and the patch below fixed it.
>
> Signed-off-by:Shaun Pereira <spereira@tusc.com.au>
Applied, thanks.
prev parent reply other threads:[~2006-04-28 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 5:03 [PATCH 1/1]x25: fix for spinlock recurse and spinlock lockup with timer handler in x25 Shaun Pereira
2006-04-28 19:00 ` David S. Miller [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=20060428.120033.86347954.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=eis@baty.hanse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=spereira@tusc.com.au \
/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