From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: davej@redhat.com, netdev@vger.kernel.org,
yoshfuji@linux-ipv6.org, mingo@elte.hu, arjan@linux.intel.com
Subject: Re: another networking lockdep trace.
Date: Wed, 09 Aug 2006 16:52:22 -0700 (PDT) [thread overview]
Message-ID: <20060809.165222.32095748.davem@davemloft.net> (raw)
In-Reply-To: <E1GAmbn-0006Ts-00@gondolin.me.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Wed, 09 Aug 2006 21:52:23 +1000
> Nice. This is a bug introduced less than 2 weeks ago. We're finally
> getting some dividends from the lock validator :) Thanks guys!
Horray! :-)
> [IPV6]: The ifa lock is a BH lock
>
> The ifa lock is expected to be taken in BH context (by addrconf timers)
> so we must disable BH when accessing it from user context.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Applied, thanks Herbert.
prev parent reply other threads:[~2006-08-09 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 18:41 another networking lockdep trace Dave Jones
2006-08-09 11:52 ` Herbert Xu
2006-08-09 23:52 ` David 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=20060809.165222.32095748.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arjan@linux.intel.com \
--cc=davej@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).