From: Patrick McHardy <kaber@trash.net>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: WARNING while bringing up macvlan
Date: Fri, 28 Mar 2008 16:00:40 +0100 [thread overview]
Message-ID: <47ED0818.3030409@trash.net> (raw)
In-Reply-To: <20080328125409.M80978@visp.net.lb>
Denys Fedoryshchenko wrote:
> To trigger just run:
> ip link add link eth0 eth2 type macvlan
> ip link set eth2 up
>
> [ 1212.916818] [<c0121038>] warn_on_slowpath+0x41/0x51
> [ 1212.916859] [<c012f652>] ? __kernel_text_address+0x1b/0x27
> [ 1212.916895] [<c010493a>] ? dump_trace+0xce/0xda
> [ 1212.916927] [<c0109ea6>] ? save_stack_address+0x0/0x2c
> [ 1212.916965] [<c013afc8>] ? mark_held_locks+0x41/0x5c
> [ 1212.916999] [<c015cdef>] ? kmem_cache_alloc+0x69/0xa1
> [ 1212.917033] [<c013b12d>] ? trace_hardirqs_on+0xcb/0x102
> [ 1212.917067] [<c02ba549>] mutex_trylock+0x3c/0xef
> [ 1212.917099] [<c0272796>] rtnl_trylock+0xd/0xf
> [ 1212.917131] [<c0268bc8>] __dev_set_promiscuity+0x15/0xa9
This is a known harmless warning caused by ASSERT_RTNL calling
rtnl_trylock. To fix this we'd need to move multicast list
programming into process context. For now you can simply
ignore it.
prev parent reply other threads:[~2008-03-28 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 13:05 WARNING while bringing up macvlan Denys Fedoryshchenko
2008-03-28 15:00 ` Patrick McHardy [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=47ED0818.3030409@trash.net \
--to=kaber@trash.net \
--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).