From: Jarek Poplawski <jarkao2@gmail.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: circular locking, mirred, 2.6.24.2
Date: Mon, 25 Feb 2008 09:56:46 +0000 [thread overview]
Message-ID: <20080225095646.GA4321@ff.dom.local> (raw)
In-Reply-To: <20080224222035.M62480@visp.net.lb>
On 24-02-2008 23:20, Denys Fedoryshchenko wrote:
> 2.6.24.2 with applied patches for printk,softlockup, and patch for htb (as i
> understand, they are in 2.6.25 git and it is fixes).
>
> I will send also to private mails QoS rules i am using.
>
> [ 118.840072] =======================================================
> [ 118.840158] [ INFO: possible circular locking dependency detected ]
> [ 118.840203] 2.6.24.2-build-0022 #7
> [ 118.840243] -------------------------------------------------------
> [ 118.840288] swapper/0 is trying to acquire lock:
> [ 118.840329] (&dev->queue_lock){-+..}, at: [<c0289c11>] dev_queue_xmit
> +0x177/0x302
> [ 118.840490]
> [ 118.840490] but task is already holding lock:
> [ 118.840567] (&p->tcfc_lock){-+..}, at: [<f89f0066>] tcf_mirred+0x20/0x180
> [act_mirred]
> [ 118.840727]
> [ 118.840727] which lock already depends on the new lock.
> [ 118.840728]
> [ 118.840842]
> [ 118.840842] the existing dependency chain (in reverse order) is:
> [ 118.840921]
> [ 118.840921] -> #2 (&p->tcfc_lock){-+..}:
> [ 118.841075] [<c0143624>] __lock_acquire+0xa30/0xc19
> [ 118.841324] [<c0143887>] lock_acquire+0x7a/0x94
> [ 118.841572] [<c02d93f5>] _spin_lock+0x2e/0x58
> [ 118.841820] [<f89f0066>] tcf_mirred+0x20/0x180 [act_mirred]
> [ 118.842068] [<c0297ec4>] tcf_action_exec+0x44/0x77
> [ 118.842344] [<f89ba5d2>] u32_classify+0x119/0x24a [cls_u32]
> [ 118.842595] [<c0295ce2>] tc_classify_compat+0x2f/0x5e
> [ 118.842845] [<c0295ec3>] tc_classify+0x1a/0x80
> [ 118.843092] [<f899c118>] ingress_enqueue+0x1a/0x53 [sch_ingress]
> [ 118.843343] [<c0287139>] netif_receive_skb+0x296/0x44c
> [ 118.843592] [<f88d1a4e>] e100_poll+0x14b/0x26a [e100]
> [ 118.843843] [<c02894bc>] net_rx_action+0xbf/0x201
> [ 118.844091] [<c012ac15>] __do_softirq+0x6f/0xe9
> [ 118.844343] [<c01078af>] do_softirq+0x61/0xc8
> [ 118.844591] [<ffffffff>] 0xffffffff
> [ 118.844840]
> [ 118.844840] -> #1 (&dev->ingress_lock){-+..}:
> [ 118.844993] [<c0143624>] __lock_acquire+0xa30/0xc19
> [ 118.845242] [<c0143887>] lock_acquire+0x7a/0x94
> [ 118.845489] [<c02d93f5>] _spin_lock+0x2e/0x58
> [ 118.845737] [<c0295387>] qdisc_lock_tree+0x1e/0x21
> [ 118.845984] [<c02953b6>] dev_init_scheduler+0xb/0x53
> [ 118.846235] [<c0288483>] register_netdevice+0x2a3/0x2fd
> [ 118.846483] [<c028850f>] register_netdev+0x32/0x3f
> [ 118.846730] [<c03ea8ee>] loopback_net_init+0x39/0x6c
> [ 118.846980] [<c02858ef>] register_pernet_operations+0x13/0x15
> [ 118.847230] [<c0285958>] register_pernet_device+0x1f/0x4c
> [ 118.847478] [<c03ea8b3>] loopback_init+0xd/0xf
> [ 118.847725] [<c03d64df>] kernel_init+0x155/0x2c6
This looks strange: are you sure your tc scripts aren't started too
early? (Or maybe there are some problems during booting?)
Regards,
Jarek P.
> [ 118.847973] [<c0105bab>] kernel_thread_helper+0x7/0x10
> [ 118.848225] [<ffffffff>] 0xffffffff
> [ 118.848472]
> [ 118.848472] -> #0 (&dev->queue_lock){-+..}:
> [ 118.848626] [<c0143514>] __lock_acquire+0x920/0xc19
> [ 118.848874] [<c0143887>] lock_acquire+0x7a/0x94
> [ 118.849122] [<c02d93f5>] _spin_lock+0x2e/0x58
> [ 118.849370] [<c0289c11>] dev_queue_xmit+0x177/0x302
> [ 118.849617] [<f89f01a5>] tcf_mirred+0x15f/0x180 [act_mirred]
> [ 118.849866] [<c0297ec4>] tcf_action_exec+0x44/0x77
> [ 118.850114] [<f89ba5d2>] u32_classify+0x119/0x24a [cls_u32]
> [ 118.850366] [<c0295ce2>] tc_classify_compat+0x2f/0x5e
> [ 118.850614] [<c0295ec3>] tc_classify+0x1a/0x80
> [ 118.850861] [<f899c118>] ingress_enqueue+0x1a/0x53 [sch_ingress]
> [ 118.851111] [<c0287139>] netif_receive_skb+0x296/0x44c
> [ 118.851360] [<f88d1a4e>] e100_poll+0x14b/0x26a [e100]
> [ 118.851612] [<c02894bc>] net_rx_action+0xbf/0x201
> [ 118.851859] [<c012ac15>] __do_softirq+0x6f/0xe9
> [ 118.852106] [<c01078af>] do_softirq+0x61/0xc8
> [ 118.852355] [<ffffffff>] 0xffffffff
...
next prev parent reply other threads:[~2008-02-25 9:55 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 22:20 circular locking, mirred, 2.6.24.2 Denys Fedoryshchenko
2008-02-25 9:56 ` Jarek Poplawski [this message]
2008-02-25 10:48 ` Denys Fedoryshchenko
2008-02-25 11:39 ` Jarek Poplawski
2008-03-05 10:45 ` Denys Fedoryshchenko
2008-03-05 13:54 ` [BUG] Probably lockdep bug " Jarek Poplawski
2008-03-06 9:41 ` Jarek Poplawski
2008-03-06 13:40 ` Jarek Poplawski
2008-03-06 13:57 ` Denys Fedoryshchenko
2008-03-06 14:27 ` jamal
2008-03-06 15:50 ` Denys Fedoryshchenko
2008-03-06 20:25 ` Jarek Poplawski
2008-03-06 20:56 ` jamal
2008-03-06 22:12 ` Jarek Poplawski
2008-03-06 23:43 ` Denys Fedoryshchenko
2008-03-07 0:09 ` jamal
2008-03-07 0:15 ` Denys Fedoryshchenko
2008-03-07 0:25 ` jamal
2008-03-07 9:31 ` Jarek Poplawski
2008-03-07 10:19 ` Denys Fedoryshchenko
2008-03-07 10:48 ` Jarek Poplawski
2008-03-07 14:58 ` jamal
2008-03-06 20:44 ` jamal
2008-03-06 13:59 ` jamal
2008-03-06 17:56 ` Jarek Poplawski
2008-03-06 20:48 ` jamal
2008-03-06 21:40 ` Jarek Poplawski
2008-03-06 23:40 ` jamal
2008-03-07 7:51 ` Jarek Poplawski
2008-03-07 8:32 ` Jarek Poplawski
2008-03-07 13:53 ` jamal
2008-03-08 8:46 ` Jarek Poplawski
2008-03-08 8:58 ` Jarek Poplawski
2008-03-08 9:56 ` Denys Fedoryshchenko
2008-03-08 10:16 ` Denys Fedoryshchenko
2008-03-08 10:43 ` Jarek Poplawski
2008-03-08 10:52 ` Jarek Poplawski
2008-03-08 11:09 ` Denys Fedoryshchenko
2008-03-08 12:02 ` Jarek Poplawski
2008-03-19 0:46 ` Denys Fedoryshchenko
2008-03-19 7:34 ` [PATCH][NET] ifb: set separate lockdep classes for queue locks Jarek Poplawski
2008-03-19 11:34 ` jamal
2008-03-19 12:20 ` Jarek Poplawski
2008-03-20 22:37 ` David Miller
2008-03-21 0:03 ` [PATCH take2][NET] " Jarek Poplawski
2008-03-21 0:05 ` David Miller
2008-03-21 0:15 ` Jarek Poplawski
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=20080225095646.GA4321@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=denys@visp.net.lb \
--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;
as well as URLs for NNTP newsgroup(s).