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: <CACPM=kUtm0i5qRWGs9yKBMDZ0fFEQ5-US6wdfa+bjh6ZB2ZhOQ@mail.gmail.com>
Date:	Sat, 18 Jan 2014 23:24:53 +0100
From:	Bjarke Istrup Pedersen <gurligebis@...too.org>
To:	Borislav Petkov <bp@...en8.de>
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

2014/1/18 Borislav Petkov <bp@...en8.de>:
> On Sat, Jan 18, 2014 at 11:07:10PM +0100, Bjarke Istrup Pedersen wrote:
>> I have been thinking about other solutions, but so far, I haven't been
>> able to find one that solves it, so the tools build. (An option might
>> be to strip it from the __KERNEL__ part, to make it smaller, but I
>> don't know what difference that would make :-)
>
> The fix is to move the userspace stuff into the uapi header and include
> that header in the kernel header.
>
> See include/linux/sched.h and many others for an example.
>
Okay, so let me see if I get this right.

I should take all the parts the is not guarded by __KERNEL__, and move
them to a uapi header, and then include it at the top of the normal
header.
Correct understood? :)

/Bjarke
> --
> 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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ