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: Fri, 3 Jun 2011 17:32:06 -0400 (EDT) From: Dave Anderson <anderson@...hat.com> To: Andi Kleen <andi@...stfloor.org> Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, jstancek@...hat.com Subject: Re: [PATCH] x86-64: Prevent gcc from optimizing away venosys_1() ----- Original Message ----- > > return 0; > > } > > > > -static long __vsyscall(3) venosys_1(void) > > +long __vsyscall(3) venosys_1(void) > > Better add a __used too. Otherwise it can be optimized out again > in some builds e.g. when someone enables gc-sections for the linker. Considering that all of the vsyscall prototypes have this attribute: #define __vsyscall(nr) \ __attribute__ ((unused, __section__(".vsyscall_" #nr))) notrace How would any of them work? Dave > > -Andi > -- > ak@...ux.intel.com -- Speaking for myself only. -- 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