vsock: Make transport the proto owner
authorAndy King <acking@vmware.com>
Thu, 1 May 2014 22:20:43 +0000 (15:20 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 31 May 2014 20:20:36 +0000 (13:20 -0700)
commit1b3ac8488ee4a5dd42b6c1809ca8e80fb64c549c
tree71aab9449494743f91d9b2f6f0119dac123d0884
parentab7ba76731a124ef9a70b07004c63b09e260b0d4
vsock: Make transport the proto owner

[ Upstream commit 2c4a336e0a3e203fab6aa8d8f7bb70a0ad968a6b ]

Right now the core vsock module is the owner of the proto family. This
means there's nothing preventing the transport module from unloading if
there are open sockets, which results in a panic. Fix that by allowing
the transport to be the owner, which will refcount it properly.

Includes version bump to 1.0.1.0-k

Passes checkpatch this time, I swear...

Acked-by: Dmitry Torokhov <dtor@vmware.com>
Signed-off-by: Andy King <acking@vmware.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
include/net/af_vsock.h
net/vmw_vsock/af_vsock.c