From: Chuck Ebbert <cebbert@redhat.com>
To: Netdev <netdev@vger.kernel.org>
Subject: Nested VLAN causes recursive locking error
Date: Tue, 18 Dec 2007 18:03:55 -0500 [thread overview]
Message-ID: <476851DB.5080107@redhat.com> (raw)
From:
https://bugzilla.redhat.com/show_bug.cgi?id=426164
kernel version is 2.6.24-0.107.rc5.git3.fc9
>From boot log on serial console:
(full log attached)
Added VLAN with VID == 2 to IF -:eth0.1568:-
=============================================
[ INFO: possible recursive locking detected ]
2.6.24-0.107.rc5.git3.fc9 #1
---------------------------------------------
ifconfig/15011 is trying to acquire lock:
(&vlan_netdev_xmit_lock_key){-+..}, at: [<c05d9450>] dev_mc_sync+0x1c/0x102
but task is already holding lock:
(&vlan_netdev_xmit_lock_key){-+..}, at: [<c05d51bd>] dev_set_rx_mode+0x14/0x3c
other info that might help us debug this:
2 locks held by ifconfig/15011:
#0: (rtnl_mutex){--..}, at: [<c05de4f7>] rtnl_lock+0xf/0x11
#1: (&vlan_netdev_xmit_lock_key){-+..}, at: [<c05d51bd>] dev_set_rx_mode+0x14/0x3c
stack backtrace:
Pid: 15011, comm: ifconfig Not tainted 2.6.24-0.107.rc5.git3.fc9 #1
[<c040649a>] show_trace_log_lvl+0x1a/0x2f
[<c0406d41>] show_trace+0x12/0x14
[<c0407061>] dump_stack+0x6c/0x72
[<c044cfb3>] __lock_acquire+0x815/0xb5f
[<c044d6f5>] lock_acquire+0x7b/0x9e
[<c063dcf5>] _spin_lock_bh+0x33/0x5d
[<c05d9450>] dev_mc_sync+0x1c/0x102
[<f8b24c96>] vlan_dev_set_multicast_list+0x15/0x17 [8021q]
[<c05d5107>] __dev_set_rx_mode+0x7e/0x81
[<c05d51d0>] dev_set_rx_mode+0x27/0x3c
[<c05d749e>] dev_open+0x61/0x7b
[<c05d60b0>] dev_change_flags+0xa4/0x152
[<c0616b8d>] devinet_ioctl+0x211/0x518
[<c061723b>] inet_ioctl+0x86/0xa4
[<c05caf0b>] sock_ioctl+0x1ca/0x1eb
[<c049cdf2>] do_ioctl+0x22/0x67
[<c049d080>] vfs_ioctl+0x249/0x25c
[<c049d0d5>] sys_ioctl+0x42/0x5d
[<c0405252>] syscall_call+0x7/0xb
=======================
next reply other threads:[~2007-12-18 23:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 23:03 Chuck Ebbert [this message]
2007-12-20 13:52 ` [PATCH] Re: Nested VLAN causes recursive locking error Jarek Poplawski
2007-12-31 15:04 ` Patrick McHardy
2007-12-31 17:45 ` Jarek Poplawski
2007-12-31 17:54 ` Jarek Poplawski
2007-12-31 21:59 ` Jarek Poplawski
2008-01-02 16:40 ` Benny Amorsen
2008-01-02 23:41 ` [PATCH take2] " Jarek Poplawski
2008-01-10 15:31 ` Patrick McHardy
2008-01-10 21:08 ` Jarek Poplawski
2008-01-10 21:33 ` 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=476851DB.5080107@redhat.com \
--to=cebbert@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.