From: David Miller <davem@davemloft.net>
To: Knut_Petersen@t-online.de
Cc: paulus@samba.org, linux-kernel@vger.kernel.org,
mostrows@earthlink.net, linux-ppp@vger.kernel.org,
xiaosuo@gmail.com, eric.dumazet@gmail.com
Subject: Re: [BUG] 2.6.38-rc2: Circular Locking Dependency
Date: Tue, 08 Feb 2011 00:07:21 -0800 (PST) [thread overview]
Message-ID: <20110208.000721.193716330.davem@davemloft.net> (raw)
In-Reply-To: <4D50F5FA.7050202@t-online.de>
From: Knut Petersen <Knut_Petersen@t-online.de>
Date: Tue, 08 Feb 2011 08:51:22 +0100
> I bisected the problem with the following result:
>
> aa9421041128abb4d269ee1dc502ff65fb3b7d69 is the first bad commit
> commit aa9421041128abb4d269ee1dc502ff65fb3b7d69
> Author: Changli Gao <xiaosuo@gmail.com>
> Date: Sat Dec 4 02:31:41 2010 +0000
>
> net: init ingress queue
>
> The dev field of ingress queue is forgot to initialized, then NULL
> pointer dereference happens in qdisc_alloc().
>
> Move inits of tx queues to netif_alloc_netdev_queues().
>
> Signed-off-by: Changli Gao <xiaosuo@gmail.com>
> Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> :040000 040000 dcbb6ab41c4308cba1bc6823d200dcf92aa402d8
> b5e190ec681d26ffe62d1d0214c4ef77b8034189 M net
Indeed, this initialization is now too early for the sake
of getting the lockdep bits right. The problem is that at
the point in which we call netif_alloc_netdev_queue() we
haven't initialized dev->type yet, it is therefore always
zero when we setup the lockdep class for ->_xmit_lock.
next prev parent reply other threads:[~2011-02-08 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 9:25 Knut Petersen
2011-02-07 7:28 ` David Miller
2011-02-07 10:29 ` Paul Mackerras
2011-02-07 10:43 ` Paul Mackerras
2011-02-08 7:51 ` Knut Petersen
2011-02-08 8:07 ` David Miller [this message]
2011-02-08 23:04 ` David Miller
2011-02-09 7:26 ` Knut Petersen
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=20110208.000721.193716330.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Knut_Petersen@t-online.de \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=mostrows@earthlink.net \
--cc=paulus@samba.org \
--cc=xiaosuo@gmail.com \
/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
all inboxes | Powered by JetHome®