summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorAndy King <acking@vmware.com>2014-05-01 22:20:43 (GMT)
committerDavid S. Miller <davem@davemloft.net>2014-05-05 17:13:50 (GMT)
commit2c4a336e0a3e203fab6aa8d8f7bb70a0ad968a6b (patch)
tree2d53ba2bdafac830dedc783d455e8c937cb8e2e7 /include
parentb8dff4e60cbbb8a3382a265797ef8554a6868f39 (diff)
downloadlinux-2c4a336e0a3e203fab6aa8d8f7bb70a0ad968a6b.tar.xz
vsock: Make transport the proto owner
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>
Diffstat (limited to 'include')
-rw-r--r--include/net/af_vsock.h6
1 files changed, 5 insertions, 1 deletions
diff --git a/include/net/af_vsock.h b/include/net/af_vsock.h
index 7d64d36..4282778 100644
--- a/include/net/af_vsock.h
+++ b/include/net/af_vsock.h
@@ -155,7 +155,11 @@ struct vsock_transport {
/**** CORE ****/
-int vsock_core_init(const struct vsock_transport *t);
+int __vsock_core_init(const struct vsock_transport *t, struct module *owner);
+static inline int vsock_core_init(const struct vsock_transport *t)
+{
+ return __vsock_core_init(t, THIS_MODULE);
+}
void vsock_core_exit(void);
/**** UTILS ****/