linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: davem@davemloft.net, mst@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: sergei.shtylyov@cogentembedded.com, Jason Wang <jasowang@redhat.com>
Subject: [net-next rfc V3 1/9] macvtap: fix a possible race between queue selection and changing queues
Date: Wed,  5 Jun 2013 14:36:24 +0800	[thread overview]
Message-ID: <1370414192-5830-2-git-send-email-jasowang@redhat.com> (raw)
In-Reply-To: <1370414192-5830-1-git-send-email-jasowang@redhat.com>

Complier may generate codes that re-read the vlan->numvtaps during
macvtap_get_queue(). This may lead a race if vlan->numvtaps were changed in the
same time and which can lead unexpected result (e.g. very huge value).

We need prevent the compiler from generating such codes by adding an
ACCESS_ONCE() to make sure vlan->numvtaps were only read once.

Signed-off-by: Jason Wang <jasowang@redhat.com>
---
 drivers/net/macvtap.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
index 68efb91..5e485e3 100644
--- a/drivers/net/macvtap.c
+++ b/drivers/net/macvtap.c
@@ -172,7 +172,7 @@ static struct macvtap_queue *macvtap_get_queue(struct net_device *dev,
 {
 	struct macvlan_dev *vlan = netdev_priv(dev);
 	struct macvtap_queue *tap = NULL;
-	int numvtaps = vlan->numvtaps;
+	int numvtaps = ACCESS_ONCE(vlan->numvtaps);
 	__u32 rxq;
 
 	if (!numvtaps)
-- 
1.7.1


  reply	other threads:[~2013-06-05  6:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  6:36 [net-next rfc V3 0/9] Multiqueue API for macvtap Jason Wang
2013-06-05  6:36 ` Jason Wang [this message]
2013-06-05 10:35   ` [net-next rfc V3 1/9] macvtap: fix a possible race between queue selection and changing queues Michael S. Tsirkin
2013-06-05  6:36 ` [net-next rfc V3 2/9] macvtap: do not add self to waitqueue if doing a nonblock read Jason Wang
2013-06-05 11:07   ` Michael S. Tsirkin
2013-06-05  6:36 ` [net-next rfc V3 3/9] macvlan: switch to use IS_ENABLED() Jason Wang
2013-06-05  6:36 ` [net-next rfc V3 4/9] macvtap: introduce macvtap_get_vlan() Jason Wang
2013-06-05  6:36 ` [net-next rfc V3 5/9] macvlan: change the max number of queues to 16 Jason Wang
2013-06-05  6:36 ` [net-next rfc V3 6/9] macvtap: eliminate linear search Jason Wang
2013-06-05  6:36 ` [net-next rfc V3 7/9] macvtap: allow TUNSETIFF to create multiqueue device Jason Wang
2013-06-05 10:43   ` Michael S. Tsirkin
2013-06-06  3:13     ` Jason Wang
2013-06-06  6:59       ` Michael S. Tsirkin
2013-06-06  7:12         ` Jason Wang
2013-06-06  7:26           ` Michael S. Tsirkin
2013-06-06  7:31             ` Jason Wang
2013-06-05  6:36 ` [net-next rfc V3 8/9] macvtap: add TUNSETQUEUE ioctl Jason Wang
2013-06-05 10:59   ` Michael S. Tsirkin
2013-06-06  3:16     ` Jason Wang
2013-06-06  7:23       ` Michael S. Tsirkin
2013-06-06  7:30         ` Jason Wang
2013-06-05  6:36 ` [net-next rfc V3 9/9] macvtap: enable multiqueue flag Jason Wang
2013-06-05 10:36 ` [net-next rfc V3 0/9] Multiqueue API for macvtap Michael S. Tsirkin
2013-06-06  3:07   ` Jason Wang

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=1370414192-5830-2-git-send-email-jasowang@redhat.com \
    --to=jasowang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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 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).