From: Chuck Ebbert <76306.1226@compuserve.com>
To: Darren Reed <darrenr@reed.wattle.id.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.11: spinlock problem
Date: Sat, 24 Jun 2006 06:18:33 -0400 [thread overview]
Message-ID: <200606240620_MC3-1-C357-8BEB@compuserve.com> (raw)
In-Reply-To: <200606240247.k5O2lU3C009083@firewall.reed.wattle.id.au>
On Sat, 24 Jun 2006 12:47:30 +1000, Darren Reed wrote:
> The call stack for the panic is:
> panic
> ipf_read_enter
> ..
> do_softirq
> =====
> do_IRQ
> common_interrupt
> ipf_rw_exit
If you are using spinlocks fron interrupt context you need to use
spin_lock_irq/spin_lock_irqsave / spin_unlock_irq/spin_unlock_irqrestore.
--
Chuck
"You can't read a newspaper if you can't read." --George W. Bush
next reply other threads:[~2006-06-24 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 10:18 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-23 16:51 2.6.11: spinlock problem Darren Reed
2006-06-23 17:34 ` linux-os (Dick Johnson)
2006-06-24 2:47 ` Darren Reed
2006-06-25 9:38 ` Frederik Deweerdt
2006-06-23 19:19 ` Hareesh Nagarajan
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=200606240620_MC3-1-C357-8BEB@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=darrenr@reed.wattle.id.au \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).