linux-kernel - Re: [PATCH] VSOCK: Support VM sockets connected to the hypervisor.

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>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20130315.082530.1920500635070584515.davem@davemloft.net>
Date:	Fri, 15 Mar 2013 08:25:30 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	grantr@...are.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	pv-drivers@...are.com
Subject: Re: [PATCH] VSOCK: Support VM sockets connected to the hypervisor.

From: Reilly Grant <grantr@...are.com>
Date: Tue, 12 Mar 2013 12:40:19 -0700

> The resource ID used for VM socket control packets (0) is already
> used for the VMCI_GET_CONTEXT_ID hypercall so a new ID (15) must be
> used when the guest sends these datagrams to the hypervisor.
> 
> The hypervisor context ID must also be removed from the internal
> blacklist.
> 
> Signed-off-by: Reilly Grant <grantr@...are.com>
> Acked-by: Andy King <acking@...are.com>

Applied, thanks.
--
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/