| 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: Mon, 17 Dec 2012 14:49:32 +0000 From: David Howells <dhowells@...hat.com> To: khali@...ux-fr.org Cc: x86@...nel.org, linux-kernel@...r.kernel.org Subject: [PATCH 2/2] x86: Provide guards in uapi/asm/setup.h to prevent deletion by patch Provide reinclusion guards in the empty uapi/asm/setup.h to make sure that the patch program doesn't delete it. However, should some part of asm/hw_setup.h actually be exported here, or, possibly, should the entire uapi file be removed? In v3.6, though the file was marked for export to userspace, it had nothing outside of __KERNEL__. Signed-off-by: David Howells <dhowells@...hat.com> cc: Jean Delvare <khali@...ux-fr.org> --- arch/x86/include/uapi/asm/setup.h | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/arch/x86/include/uapi/asm/setup.h b/arch/x86/include/uapi/asm/setup.h index e69de29..96a4d53 100644 --- a/arch/x86/include/uapi/asm/setup.h +++ b/arch/x86/include/uapi/asm/setup.h @@ -0,0 +1,4 @@ +#ifndef _UAPI_ASM_X86_SETUP_H +#define _UAPI_ASM_X86_SETUP_H + +#endif /* _UAPI_ASM_X86_SETUP_H */ -- 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