linux-kernel - [PATCH 1/8] virtio_net: do not export "u16" to userspace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 01 Apr 2013 19:56:32 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Jason Wang <jasowang@...hat.com>,
	Krishna Kumar <krkumar2@...ibm.com>,
	"David S. Miller" <davem@...emloft.net>
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH 1/8] virtio_net: do not export "u16" to userspace

Building the lguest (userspace) tool fails with this error:
    In file included from lguest.c:46:0:
    /usr/include/linux/virtio_net.h:188:2: error: unknown type name ‘u16’
    make: *** [lguest] Error 1

virtio_net.h exports "u16" to userspace. Use "__u16" instead of "u16".

Signed-off-by: Paul Bolle <pebolle@...cali.nl>
---
"u16" was added here in commit 986a4f4d452dec004697f667439d27c3fda9c928
("virtio_net: multiqueue support"). That commit was shipped in v3.8. So
if this patch ends up in the tree it should also be sent to stable.

 include/uapi/linux/virtio_net.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/uapi/linux/virtio_net.h b/include/uapi/linux/virtio_net.h
index a5a8c88..c520203 100644
--- 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
-- 
1.7.11.7

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/