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
| ||
|
Date: Wed, 28 Dec 2016 20:09:44 +0300 From: Roman Kagan <rkagan@...tuozzo.com> To: KY Srinivasan <kys@...rosoft.com> CC: Stephen Hemminger <stephen@...workplumber.org>, Christoph Hellwig <hch@...radead.org>, Paolo Bonzini <pbonzini@...hat.com>, Radim Krčmář <rkrcmar@...hat.com>, Vitaly Kuznetsov <vkuznets@...hat.com>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "Denis V . Lunev" <den@...nvz.org>, Haiyang Zhang <haiyangz@...rosoft.com>, "x86@...nel.org" <x86@...nel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH 12/15] hyperv: move VMBus connection ids to uapi On Wed, Dec 21, 2016 at 07:54:11PM +0000, KY Srinivasan wrote: > > > > -----Original Message----- > > From: Stephen Hemminger [mailto:stephen@...workplumber.org] > > Sent: Wednesday, December 21, 2016 10:03 AM > > To: Christoph Hellwig <hch@...radead.org> > > Cc: Paolo Bonzini <pbonzini@...hat.com>; Roman Kagan > > <rkagan@...tuozzo.com>; Radim Krčmář <rkrcmar@...hat.com>; KY > > Srinivasan <kys@...rosoft.com>; Vitaly Kuznetsov > > <vkuznets@...hat.com>; kvm@...r.kernel.org; Denis V . Lunev > > <den@...nvz.org>; Haiyang Zhang <haiyangz@...rosoft.com>; > > x86@...nel.org; linux-kernel@...r.kernel.org; Ingo Molnar > > <mingo@...hat.com>; H. Peter Anvin <hpa@...or.com>; > > devel@...uxdriverproject.org; Thomas Gleixner <tglx@...utronix.de> > > Subject: Re: [PATCH 12/15] hyperv: move VMBus connection ids to uapi > > > > On Wed, 21 Dec 2016 09:58:36 -0800 > > Christoph Hellwig <hch@...radead.org> wrote: > > > > > On Wed, Dec 21, 2016 at 09:50:49AM -0800, Stephen Hemminger wrote: > > > > Lastly, there is licensing issues on headers. It would be good to have any > > > > userspace ABI headers licensed with a more liberal license so that BSD > > and DPDK drivers > > > > could use them directly. Right now each one reinvents. > > > > > > Microsoft could easily solves this problem by offering a suitably > > > liberally licensed header documenting the full HyperV guest protocol > > > that Linux and other projects could use. > > > > The issue is if same header file mixes kernel and userspace API stuff. > > > > Once the files are arranged right, I will submit trivial change to comments > > to indicate the liberal licensing of userspace API headers. > > Let us take this one step at a time. I know for a fact that not all the guest host > protocols on Hyper-V are guaranteed to be stable. Some of the protocols are part of > the published MSFT standards such RNDIS and these obviously are guaranteed to be > stable. For the rest it is less clear. The fact that we need to ensure compatibility of existing > Windows guests tells me that any host side changes will be versioned and the hosts will always > support older guests. > > I would like to minimize what we include in the uapi header; especially when MSFT has made no guarantees > with regards how they may be evolved. I will also work on getting some clarity on both stability and > under what license we would expose the uapi header. Am I correct assuming that QEMU is currently the only user of arch/x86/include/uapi/asm/hyperv.h? Then I think we're fine withdrawing it from uapi as a whole and letting QEMU pull it in through its header-harvesting scripts (as does now anyway). This would lift all licensing and longterm API stability expectations. Roman.
Powered by blists - more mailing lists