This is a note to let you know that I've just added the patch titled

    virtio: don't expose u16 in userspace api

to the 3.9-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     virtio-don-t-expose-u16-in-userspace-api.patch
and it can be found in the queue-3.9 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From 948c8d59ef7602f98752e37d1ace34cdd89b3816 Mon Sep 17 00:00:00 2001
From: stephen hemminger <[email protected]>
Date: Fri, 3 May 2013 14:49:41 +0000
Subject: virtio: don't expose u16 in userspace api


From: stephen hemminger <[email protected]>

[ Upstream commit 77d21f23a1e4db8639e3916547c903a3b3c7a07c ]

Programs using virtio headers outside of kernel will no longer
build because u16 type does not exist in userspace. All user ABI
must use __u16 typedef instead.

Bug introduce by:
  commit 986a4f4d452dec004697f667439d27c3fda9c928
  Author: Jason Wang <[email protected]>
  Date:   Fri Dec 7 07:04:56 2012 +0000

    virtio_net: multiqueue support

Signed-off-by: Stephen Hemminger <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
 include/uapi/linux/virtio_net.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/include/uapi/linux/virtio_net.h
+++ b/include/uapi/linux/virtio_net.h
@@ -191,7 +191,7 @@ struct virtio_net_ctrl_mac {
  * specified.
  */
 struct virtio_net_ctrl_mq {
-       u16 virtqueue_pairs;
+       __u16 virtqueue_pairs;
 };
 
 #define VIRTIO_NET_CTRL_MQ   4


Patches currently in stable-queue which might be from 
[email protected] are

queue-3.9/bridge-fix-race-with-topology-change-timer.patch
queue-3.9/virtio-don-t-expose-u16-in-userspace-api.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to