linux-kernel - Re: [PATCH] Adding hyperv.h to uapi headers

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]

Message-ID: <20140118234611.GJ15466@pd.tnic>
Date:	Sun, 19 Jan 2014 00:46:11 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Bjarke Istrup Pedersen <gurligebis@...too.org>
Cc:	Paul Bolle <pebolle@...cali.nl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Haiyang Zhang <haiyangz@...rosoft.com>,
	"K. Y. Srinivasan" <kys@...rosoft.com>
Subject: Re: [PATCH] Adding hyperv.h to uapi headers

On Sun, Jan 19, 2014 at 12:24:10AM +0100, Bjarke Istrup Pedersen wrote:
> I have submitted a v2 patch - does it look better?

If you mean this:

 include/linux/hyperv.h      | 321 +----------------------------------------
 include/uapi/linux/Kbuild   |   1 +
 include/uapi/linux/hyperv.h | 344 ++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 347 insertions(+), 319 deletions(-)
 create mode 100644 include/uapi/linux/hyperv.h

you've got the rough idea of uapi headers :-).

Whether that makes sense at all in the hyperv case, you'll have to wait
for the hyperv guys to say something.

What makes me wonder is why do you need to export this now?

Because if those userspace hyperv tools would really need the
definitions in that header, then they never did build before. Which
would be really stupid. Btw, which userspace hyperv tools do you mean?
Where are they?

What am I missing?

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/