Fwd: 3.3.0, 3.4-rc1 reproducible tun Oops
|Target version:||1st Public Cerowrt release|
---------- Forwarded message ----------
From: Simon Kirby <firstname.lastname@example.org>
Date: Tue, Apr 17, 2012 at 3:08 AM
Subject: Re: 3.3.0, 3.4-rc1 reproducible tun Oops
To: Eric Dumazet <email@example.com>, Stanislav Kinsbursky
On Thu, Apr 05, 2012 at 04:41:04AM +0200, Eric Dumazet wrote:
Hmm, is it happening if you remove the nvidia module ?
If yes, please try to add slub_debug=FZPU
Finally got annoyed enough at this to bisect it. It doesn't happen every
time and I got a bit confused, but I finally tracked it down to:
1ab5ecb90cb6a3df1476e052f76a6e8f6511cb3d is the first bad commit
Author: Stanislav Kinsbursky <firstname.lastname@example.org>
Date: Mon Mar 12 02:59:41 2012 +0000
tun: don't hold network namespace by tun sockets
v3: added previously removed sock_put() to the tun_release()
sk_release_kernel() doesn't drop the socket reference.
v2: sk_release_kernel() used for socket release. Dummy tun_release() is
required for sk_release_kernel() ---> sock_release() --->
TUN was designed to destroy it's socket on network namesapce
shutdown. But this
will never happen for persistent device, because it's socket holds network
This patch removes of holding network namespace by TUN socket and replaces it
by creating socket in init_net and then changing it's net it to
desired one. On
shutdown socket is moved back to init_net prior to final put.
...With this reverted on top of 3.4-rc3, I no longer see crashes when I
keep making and breaking the SSH tunnel while running "vmstat 1" in an
SSH session over a socket that is running through that tunnel.