From: David Miller <davem@davemloft.net>
To: acking@vmware.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
gregkh@linuxfoundation.org, pv-drivers@vmware.com,
stable@vger.kernel.org
Subject: Re: [PATCH] vsock: Make transport the proto owner
Date: Mon, 05 May 2014 13:14:37 -0400 (EDT) [thread overview]
Message-ID: <20140505.131437.1075882730518482984.davem@davemloft.net> (raw)
In-Reply-To: <1398982843-1453-1-git-send-email-acking@vmware.com>
From: Andy King <acking@vmware.com>
Date: Thu, 1 May 2014 15:20:43 -0700
> 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...
>
> Cc: stable@vger.kernel.org
Please do not explicitly CC: stable for networking submissions, instead please
just ask me to queue it up for -stable submission since I handle networking
-stable myself.
> Acked-by: Dmitry Torokhov <dtor@vmware.com>
> Signed-off-by: Andy King <acking@vmware.com>
Applied, thanks.
next prev parent reply other threads:[~2014-05-05 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 22:20 [PATCH] vsock: Make transport the proto owner Andy King
2014-05-05 17:14 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-01 22:09 Andy King
2014-05-01 22:10 ` Andy King
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=20140505.131437.1075882730518482984.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acking@vmware.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).