From: David Miller <davem@davemloft.net>
To: john.r.fastabend@intel.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [net-next-2.6 PATCH] 8021q: vlan device is lockless do not transfer real_num_{tx|rx}_queues
Date: Sun, 28 Nov 2010 10:48:33 -0800 (PST) [thread overview]
Message-ID: <20101128.104833.112592379.davem@davemloft.net> (raw)
In-Reply-To: <20101124231450.3158.67194.stgit@jf-dev1-dcblab>
From: John Fastabend <john.r.fastabend@intel.com>
Date: Wed, 24 Nov 2010 15:14:50 -0800
> Now that the vlan device is lockless and single queue do not
> transfer the real num queues. This is causing a BUG_ON to occur.
>
> kernel BUG at net/8021q/vlan.c:345!
> Call Trace:
> [<ffffffff813fd6e8>] ? fib_rules_event+0x28/0x1b0
> [<ffffffff814ad2b5>] notifier_call_chain+0x55/0x80
> [<ffffffff81089156>] raw_notifier_call_chain+0x16/0x20
> [<ffffffff813e5af7>] call_netdevice_notifiers+0x37/0x70
> [<ffffffff813e6756>] netdev_features_change+0x16/0x20
> [<ffffffffa02995be>] ixgbe_fcoe_enable+0xae/0x100 [ixgbe]
> [<ffffffffa01da06a>] vlan_dev_fcoe_enable+0x2a/0x30 [8021q]
> [<ffffffffa02d08c3>] fcoe_create+0x163/0x630 [fcoe]
> [<ffffffff811244d5>] ? mmap_region+0x255/0x5a0
> [<ffffffff81080ef0>] param_attr_store+0x50/0x80
> [<ffffffff810809b6>] module_attr_store+0x26/0x30
> [<ffffffff811b9db2>] sysfs_write_file+0xf2/0x180
> [<ffffffff8114fc88>] vfs_write+0xc8/0x190
> [<ffffffff81150621>] sys_write+0x51/0x90
> [<ffffffff8100c0b2>] system_call_fastpath+0x16/0x1b
>
> Signed-off-by: John Fastabend <john.r.fastabend@intel.com>
Applied.
prev parent reply other threads:[~2010-11-28 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 23:14 [net-next-2.6 PATCH] 8021q: vlan device is lockless do not transfer real_num_{tx|rx}_queues John Fastabend
2010-11-28 18:48 ` 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=20101128.104833.112592379.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=john.r.fastabend@intel.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 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).