From: Andy King <acking@vmware.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Cc: pv-drivers@vmware.com, gregkh@linuxfoundation.org,
davem@davemloft.net, stable@vger.kernel.org
Subject: Re: [PATCH] vsock: Make transport the proto owner
Date: Thu, 1 May 2014 15:10:19 -0700 (PDT) [thread overview]
Message-ID: <2052779979.17092541.1398982219130.JavaMail.root@vmware.com> (raw)
In-Reply-To: <1398982153-31436-1-git-send-email-acking@vmware.com>
Oh just shoot me now, doesn't even pass checkpatch *hangs head in shame*
Dave/Greg, flame away if you like...
- Andy
----- Original Message -----
> 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
>
> Cc: stable@vger.kernel.org
> Acked-by: Dmitry Torokhov <dtor@vmware.com>
> Signed-off-by: Andy King <acking@vmware.com>
> ---
> include/net/af_vsock.h | 6 +++++-
> net/vmw_vsock/af_vsock.c | 46
> +++++++++++++++++++++-------------------------
> 2 files changed, 26 insertions(+), 26 deletions(-)
>
> diff --git a/include/net/af_vsock.h b/include/net/af_vsock.h
> index 7d64d36..8f02e5c 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 ****/
> diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
> index 5adfd94..5743553 100644
> --- a/net/vmw_vsock/af_vsock.c
> +++ b/net/vmw_vsock/af_vsock.c
> @@ -1925,9 +1925,22 @@ static struct miscdevice vsock_device = {
> .fops = &vsock_device_ops,
> };
>
> -static int __vsock_core_init(void)
> +int __vsock_core_init(const struct vsock_transport *t, struct module *owner)
> {
> - int err;
> + int err = mutex_lock_interruptible(&vsock_register_mutex);
> + if (err)
> + return err;
> +
> + if (transport) {
> + err = -EBUSY;
> + goto err_busy;
> + }
> +
> + /* Transport must be the owner of the protocol so that it can't
> + * unload while there are open sockets.
> + */
> + vsock_proto.owner = owner;
> + transport = t;
>
> vsock_init_tables();
>
> @@ -1951,36 +1964,19 @@ static int __vsock_core_init(void)
> goto err_unregister_proto;
> }
>
> + mutex_unlock(&vsock_register_mutex);
> return 0;
>
> err_unregister_proto:
> proto_unregister(&vsock_proto);
> err_misc_deregister:
> misc_deregister(&vsock_device);
> - return err;
> -}
> -
> -int vsock_core_init(const struct vsock_transport *t)
> -{
> - int retval = mutex_lock_interruptible(&vsock_register_mutex);
> - if (retval)
> - return retval;
> -
> - if (transport) {
> - retval = -EBUSY;
> - goto out;
> - }
> -
> - transport = t;
> - retval = __vsock_core_init();
> - if (retval)
> - transport = NULL;
> -
> -out:
> + transport = NULL;
> +err_busy:
> mutex_unlock(&vsock_register_mutex);
> - return retval;
> + return err;
> }
> -EXPORT_SYMBOL_GPL(vsock_core_init);
> +EXPORT_SYMBOL_GPL(__vsock_core_init);
>
> void vsock_core_exit(void)
> {
> @@ -2000,5 +1996,5 @@ EXPORT_SYMBOL_GPL(vsock_core_exit);
>
> MODULE_AUTHOR("VMware, Inc.");
> MODULE_DESCRIPTION("VMware Virtual Socket Family");
> -MODULE_VERSION("1.0.0.0-k");
> +MODULE_VERSION("1.0.1.0-k");
> MODULE_LICENSE("GPL v2");
> --
> 1.7.4.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Andy King <acking@vmware.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Cc: gregkh@linuxfoundation.org, davem@davemloft.net,
pv-drivers@vmware.com, stable@vger.kernel.org
Subject: Re: [PATCH] vsock: Make transport the proto owner
Date: Thu, 1 May 2014 15:10:19 -0700 (PDT) [thread overview]
Message-ID: <2052779979.17092541.1398982219130.JavaMail.root@vmware.com> (raw)
In-Reply-To: <1398982153-31436-1-git-send-email-acking@vmware.com>
Oh just shoot me now, doesn't even pass checkpatch *hangs head in shame*
Dave/Greg, flame away if you like...
- Andy
----- Original Message -----
> 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
>
> Cc: stable@vger.kernel.org
> Acked-by: Dmitry Torokhov <dtor@vmware.com>
> Signed-off-by: Andy King <acking@vmware.com>
> ---
> include/net/af_vsock.h | 6 +++++-
> net/vmw_vsock/af_vsock.c | 46
> +++++++++++++++++++++-------------------------
> 2 files changed, 26 insertions(+), 26 deletions(-)
>
> diff --git a/include/net/af_vsock.h b/include/net/af_vsock.h
> index 7d64d36..8f02e5c 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 ****/
> diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
> index 5adfd94..5743553 100644
> --- a/net/vmw_vsock/af_vsock.c
> +++ b/net/vmw_vsock/af_vsock.c
> @@ -1925,9 +1925,22 @@ static struct miscdevice vsock_device = {
> .fops = &vsock_device_ops,
> };
>
> -static int __vsock_core_init(void)
> +int __vsock_core_init(const struct vsock_transport *t, struct module *owner)
> {
> - int err;
> + int err = mutex_lock_interruptible(&vsock_register_mutex);
> + if (err)
> + return err;
> +
> + if (transport) {
> + err = -EBUSY;
> + goto err_busy;
> + }
> +
> + /* Transport must be the owner of the protocol so that it can't
> + * unload while there are open sockets.
> + */
> + vsock_proto.owner = owner;
> + transport = t;
>
> vsock_init_tables();
>
> @@ -1951,36 +1964,19 @@ static int __vsock_core_init(void)
> goto err_unregister_proto;
> }
>
> + mutex_unlock(&vsock_register_mutex);
> return 0;
>
> err_unregister_proto:
> proto_unregister(&vsock_proto);
> err_misc_deregister:
> misc_deregister(&vsock_device);
> - return err;
> -}
> -
> -int vsock_core_init(const struct vsock_transport *t)
> -{
> - int retval = mutex_lock_interruptible(&vsock_register_mutex);
> - if (retval)
> - return retval;
> -
> - if (transport) {
> - retval = -EBUSY;
> - goto out;
> - }
> -
> - transport = t;
> - retval = __vsock_core_init();
> - if (retval)
> - transport = NULL;
> -
> -out:
> + transport = NULL;
> +err_busy:
> mutex_unlock(&vsock_register_mutex);
> - return retval;
> + return err;
> }
> -EXPORT_SYMBOL_GPL(vsock_core_init);
> +EXPORT_SYMBOL_GPL(__vsock_core_init);
>
> void vsock_core_exit(void)
> {
> @@ -2000,5 +1996,5 @@ EXPORT_SYMBOL_GPL(vsock_core_exit);
>
> MODULE_AUTHOR("VMware, Inc.");
> MODULE_DESCRIPTION("VMware Virtual Socket Family");
> -MODULE_VERSION("1.0.0.0-k");
> +MODULE_VERSION("1.0.1.0-k");
> MODULE_LICENSE("GPL v2");
> --
> 1.7.4.1
>
next prev parent reply other threads:[~2014-05-01 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 22:09 [PATCH] vsock: Make transport the proto owner Andy King
2014-05-01 22:10 ` Andy King [this message]
2014-05-01 22:10 ` Andy King
-- strict thread matches above, loose matches on Subject: below --
2014-05-01 22:09 Andy King
2014-05-01 22:20 Andy King
2014-05-01 22:20 ` Andy King
2014-05-05 17:14 ` David Miller
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=2052779979.17092541.1398982219130.JavaMail.root@vmware.com \
--to=acking@vmware.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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.