From: Jason Wang <jasowang@redhat.com>
To: Vladislav Yasevich <vyasevich@gmail.com>, netdev@vger.kernel.org
Cc: Vladislav Yasevich <vyasevic@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] macvtap: Fix race between device delete and open.
Date: Tue, 23 Sep 2014 10:56:53 +0800 [thread overview]
Message-ID: <5420E175.3050901@redhat.com> (raw)
In-Reply-To: <1411418057-18937-1-git-send-email-vyasevic@redhat.com>
On 09/23/2014 04:34 AM, Vladislav Yasevich wrote:
> In macvtap device delete and open calls can race and
> this causes a list curruption of the vlan queue_list.
>
> The race intself is triggered by the idr accessors
> that located the vlan device. The device is stored
> into and removed from the idr under both an rtnl and
> a mutex. However, when attempting to locate the device
> in idr, only a mutex is taken. As a result, once cpu
> perfoming a delete may take an rtnl and wait for the mutex,
> while another cput doing an open() will take the idr
> mutex first to fetch the device pointer and later take
> an rtnl to add a queue for the device which may have
> just gotten deleted.
>
> With this patch, we now hold the rtnl for the duration
> of the macvtap_open() call thus making sure that
> open will not race with delete.
>
> CC: Michael S. Tsirkin <mst@redhat.com>
> CC: Jason Wang <jasowang@redhat.com>
> Signed-off-by: Vladislav Yasevich <vyasevic@redhat.com>
> ---
> drivers/net/macvtap.c | 18 ++++++++----------
> 1 file changed, 8 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
> index 3381c4f..0c6adaa 100644
> --- a/drivers/net/macvtap.c
> +++ b/drivers/net/macvtap.c
> @@ -112,17 +112,15 @@ out:
> return err;
> }
>
> +/* Requires RTNL */
> static int macvtap_set_queue(struct net_device *dev, struct file *file,
> struct macvtap_queue *q)
> {
> struct macvlan_dev *vlan = netdev_priv(dev);
> - int err = -EBUSY;
>
> - rtnl_lock();
> if (vlan->numqueues == MAX_MACVTAP_QUEUES)
> - goto out;
> + return -EBUSY;
>
> - err = 0;
> rcu_assign_pointer(q->vlan, vlan);
> rcu_assign_pointer(vlan->taps[vlan->numvtaps], q);
> sock_hold(&q->sk);
> @@ -136,9 +134,7 @@ static int macvtap_set_queue(struct net_device *dev, struct file *file,
> vlan->numvtaps++;
> vlan->numqueues++;
>
> -out:
> - rtnl_unlock();
> - return err;
> + return 0;
> }
>
> static int macvtap_disable_queue(struct macvtap_queue *q)
> @@ -454,11 +450,12 @@ static void macvtap_sock_destruct(struct sock *sk)
> static int macvtap_open(struct inode *inode, struct file *file)
> {
> struct net *net = current->nsproxy->net_ns;
> - struct net_device *dev = dev_get_by_macvtap_minor(iminor(inode));
> + struct net_device *dev;
> struct macvtap_queue *q;
> - int err;
> + int err = -ENODEV;
>
> - err = -ENODEV;
> + rtnl_lock();
> + dev = dev_get_by_macvtap_minor(iminor(inode));
> if (!dev)
> goto out;
>
> @@ -498,6 +495,7 @@ out:
> if (dev)
> dev_put(dev);
>
> + rtnl_unlock();
> return err;
> }
>
Acked-by: Jason Wang <jasowang@redhat.com>
next prev parent reply other threads:[~2014-09-23 2:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 20:34 [PATCH] macvtap: Fix race between device delete and open Vladislav Yasevich
2014-09-23 2:56 ` Jason Wang [this message]
2014-09-23 8:31 ` Michael S. Tsirkin
2014-09-26 19:21 ` 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=5420E175.3050901@redhat.com \
--to=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.com \
--cc=vyasevich@gmail.com \
/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.