Comment the lack of locking of the elf data extracted from the ELF headers
passed to UML.
Signed-off-by: Jeff Dike <[email protected]>
--
arch/um/os-Linux/elf_aux.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Index: linux-2.6.18-mm/arch/um/os-Linux/elf_aux.c
===================================================================
--- linux-2.6.18-mm.orig/arch/um/os-Linux/elf_aux.c 2006-06-17 21:49:35.000000000 -0400
+++ linux-2.6.18-mm/arch/um/os-Linux/elf_aux.c 2007-01-09 15:33:31.000000000 -0500
@@ -21,12 +21,11 @@ typedef Elf32_auxv_t elf_auxv_t;
typedef Elf64_auxv_t elf_auxv_t;
#endif
+/* These are initialized very early in boot and never changed */
char * elf_aux_platform;
long elf_aux_hwcap;
-
unsigned long vsyscall_ehdr;
unsigned long vsyscall_end;
-
unsigned long __kernel_vsyscall;
__init void scan_elf_aux( char **envp)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
