lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 16 Jul 2013 16:31:56 -0700
From:	Stephen Hemminger <>
To:	David Miller <>
Subject: Re: [PATCH net-next v2] vxlan: Fix kernel crash on rmmod.

On Thu, 11 Jul 2013 11:46:17 -0700 (PDT)
David Miller <> wrote:

> From: Pravin B Shelar <>
> Date: Thu, 11 Jul 2013 11:38:06 -0700
> > vxlan exit module unregisters vxlan net and then it unregisters
> > rtnl ops which triggers vxlan_dellink() from __rtnl_kill_links().
> > vxlan_dellink() deletes vxlan-dev from vxlan_list which has
> > list-head in vxlan-net-struct but that is already gone due to
> > net-unregister. That is how we are getting following crash.
> > 
> > Following commit fixes the crash by fixing module exit path.
>  ...
> > Signed-off-by: Pravin B Shelar <>
> Applied, thanks for fixing the commit message.

This now crashes for me with

# Test 4a new - up - rmmod
ip li add vxlan3 type vxlan id 42 group dev eth0
ip li set dev vxlan3 up
sleep 2
rmmod vxlan

The root cause is that rtnl_kill_links calls dellink even if device is still
UP. Since this a generic problem (several other tunnels will crash or leak
if rmmod when up), I am working on a generic fix.

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists