| 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: Thu, 28 Jul 2011 16:52:07 +0100 From: David Howells <dhowells@...hat.com> To: torvalds@...l.org Cc: linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org, David Howells <dhowells@...hat.com> Subject: [PATCH 17/40] UAPI: Fix E820_X_MAX ordering problem [ver #3] There's an ordering problem around the definition of E820_X_MAX: the definition in the kernel-specific header is referred to in the user-specific header data structures, at least for x86. When compiling userspace, the user-specific header provides an alternate version of E820_X_MAX. To get around this problem, place a marker specifically to indicate the point at which the UAPI header should be included in the kernel-specific file. The marker will be deleted later. Signed-off-by: David Howells <dhowells@...hat.com> --- arch/x86/include/asm/e820.h | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/arch/x86/include/asm/e820.h b/arch/x86/include/asm/e820.h index 908b969..e02512f 100644 --- a/arch/x86/include/asm/e820.h +++ b/arch/x86/include/asm/e820.h @@ -45,6 +45,8 @@ #define E820_NVS 4 #define E820_UNUSABLE 5 +// DISINTEGRATE: INCLUDE UAPI HERE + /* * reserved RAM used by kernel itself * if CONFIG_INTEL_TXT is enabled, memory of this type will be -- 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