From: Eric Dumazet <eric.dumazet@gmail.com>
To: Daniel Lezcano <daniel.lezcano@free.fr>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: kernel hangs when removing a dummy netdev with an attached macvlan
Date: Tue, 24 Aug 2010 19:01:52 +0200 [thread overview]
Message-ID: <1282669312.2477.262.camel@edumazet-laptop> (raw)
In-Reply-To: <4C73F419.2050204@free.fr>
Le mardi 24 août 2010 à 18:32 +0200, Daniel Lezcano a écrit :
> Hi all,
>
> I noticed the kernel hangs when we create a dummy interface, assign a
> macvlan on it and then delete the dummy interface.
>
> How to reproduce:
>
> ip link add dummy0 type dummy
> ip link add mc0 link dummy0 type macvlan
> ip link del dummy0
>
Strange, I could not reproduce it with linux-2.6 current tree
> That triggers:
>
> Call Trace:
> Code: 8b 84 24 08 08 00 00 49 81 c4 08 08 00 00 48 83 e8 08 48 8b 58 08
> 48 83 eb 08 eb 1a 48 8b 38 31 f6 48 8b 87 c8 05 00 00 ff 50 50 <48> 8b
> 53 08 48 89 d8 48 8d 5a f8 48 8d 50 08 49 39 d4 75 dd 5a
> Kernel panic - not syncing: softlockup: hung tasks
> ------------[ cut here ]------------
> WARNING: at kernel/lockdep.c:2322 trace_hardirqs_on_caller+0xb8/0x13b()
> Hardware name: Bochs
> Modules linked in:
> Pid: 3915, comm: ip Not tainted 2.6.34 #468
> Call Trace:
> <IRQ> [<ffffffff8102b2c0>] warn_slowpath_common+0x77/0x8f
> [<ffffffff814002dd>] ? panic+0xda/0xe7
> [<ffffffff8102b2e7>] warn_slowpath_null+0xf/0x11
> [<ffffffff81051b9f>] trace_hardirqs_on_caller+0xb8/0x13b
> [<ffffffff81051c2f>] trace_hardirqs_on+0xd/0xf
> [<ffffffff814002dd>] panic+0xda/0xe7
> [<ffffffff81076538>] softlockup_tick+0x164/0x16d
> [<ffffffff81038334>] run_local_timers+0x18/0x1a
> [<ffffffff81038357>] update_process_times+0x21/0x47
> [<ffffffff8104ec6f>] T.289+0x63/0x65
> [<ffffffff8104ec80>] tick_handle_periodic+0xf/0x57
> [<ffffffff8101330e>] smp_apic_timer_interrupt+0x74/0x86
> [<ffffffff81003493>] apic_timer_interrupt+0x13/0x20
> <EOI> [<ffffffff812fd7c4>] ? macvlan_device_event+0x101/0x11f
> [<ffffffff812fd7c4>] ? macvlan_device_event+0x101/0x11f
> [<ffffffff81405d7b>] notifier_call_chain+0x32/0x5e
> [<ffffffff81048ad8>] raw_notifier_call_chain+0xf/0x11
> [<ffffffff81339942>] call_netdevice_notifiers+0x16/0x18
> [<ffffffff8133a22c>] rollback_registered_many+0x11b/0x205
> [<ffffffff8133a393>] rollback_registered+0x2c/0x33
> [<ffffffff8133a3f7>] unregister_netdevice_queue+0x5d/0x7c
> [<ffffffff81342b17>] rtnl_dellink+0xab/0xc0
> [<ffffffff8134433c>] rtnetlink_rcv_msg+0x1c1/0x1de
> [<ffffffff8134417b>] ? rtnetlink_rcv_msg+0x0/0x1de
> [<ffffffff813536e3>] netlink_rcv_skb+0x3e/0x8f
> [<ffffffff81344174>] rtnetlink_rcv+0x21/0x28
> [<ffffffff81353403>] netlink_unicast+0x226/0x29c
> [<ffffffff81353ea8>] netlink_sendmsg+0x269/0x278
> [<ffffffff813287fa>] sock_sendmsg+0xd3/0xf4
> [<ffffffff810ae5b8>] ? might_fault+0x4c/0x9c
> [<ffffffff810ae5b8>] ? might_fault+0x4c/0x9c
> [<ffffffff810ae601>] ? might_fault+0x95/0x9c
> [<ffffffff810ae5b8>] ? might_fault+0x4c/0x9c
> [<ffffffff81332622>] ? verify_iovec+0x59/0x97
> [<ffffffff81328a61>] sys_sendmsg+0x209/0x273
> [<ffffffff8104823c>] ? up_read+0x1e/0x36
> [<ffffffff81405d0c>] ? do_page_fault+0x329/0x366
> [<ffffffff810b5921>] ? do_brk+0x23f/0x322
> [<ffffffff81051bf8>] ? trace_hardirqs_on_caller+0x111/0x13b
> [<ffffffff81402643>] ? trace_hardirqs_on_thunk+0x3a/0x3f
> [<ffffffff81002ae8>] system_call_fastpath+0x16/0x1b
> ---[ end trace 34536d0c9f1bbf5b ]---
>
next prev parent reply other threads:[~2010-08-24 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 16:32 kernel hangs when removing a dummy netdev with an attached macvlan Daniel Lezcano
2010-08-24 17:01 ` Eric Dumazet [this message]
2010-08-24 19:14 ` Daniel Lezcano
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=1282669312.2477.262.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=daniel.lezcano@free.fr \
--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.