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] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 5 Jul 2016 06:46:24 +0000
From:	Dexuan Cui <decui@...rosoft.com>
To:	David Miller <davem@...emloft.net>,
	"olaf@...fle.de" <olaf@...fle.de>,
	"vkuznets@...hat.com" <vkuznets@...hat.com>,
	"cavery@...hat.com" <cavery@...hat.com>,
	KY Srinivasan <kys@...rosoft.com>,
	"rolf.neugebauer@...ker.com" <rolf.neugebauer@...ker.com>
CC:	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"apw@...onical.com" <apw@...onical.com>,
	"jasowang@...hat.com" <jasowang@...hat.com>,
	Haiyang Zhang <haiyangz@...rosoft.com>,
	"joe@...ches.com" <joe@...ches.com>
Subject: RE: [PATCH v14 net-next 1/1] hv_sock: introduce Hyper-V Sockets

> From: David Miller [mailto:davem@...emloft.net]
> Sent: Tuesday, July 5, 2016 14:27
> To: Dexuan Cui <decui@...rosoft.com>
> Subject: Re: [PATCH v14 net-next 1/1] hv_sock: introduce Hyper-V Sockets
> 
> From: Dexuan Cui <decui@...rosoft.com>
> Date: Tue, 5 Jul 2016 01:58:31 +0000
> 
> > Not sure if you had a chance to review this version.
> 
> Why me?
I just think you're the most responsive reviewer. :-)

> Other people have to review this too.
Sure. Let me try to ask more people to review this.
 
> > Now I have a question: may I split the include/linux/socket.h change
> > and ask you to pre-allocate the number for AF_HYPERV to allow
> > backporting of Hyper-V Sockets to distro kernels, and to make sure
> > that applications using the socket type will work with the backport
> > as well as the upstream kernel?
> 
> Sorry, I'm not going to do this.
> 
> You cannot commit anything in userspace to this value anywhere
> until it is accepted upstream.
Got it. Thanks for the explanation! 

Thanks,
-- Dexuan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ