linux-kernel - Re: make headers_install headers problem on sparc64

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] [day] [month] [year] [list]

Date:	Thu, 19 Oct 2006 09:03:11 +0000
From:	andrew@...rond.org
To:	linux-kernel@...r.kernel.org
Subject: Re: make headers_install headers problem on sparc64

On Thu, Oct 19, 2006 at 08:50:22AM +0100, David Woodhouse wrote:
> 
> Hm, yes. There's still a lot of crap being exposed there that we really
> don't need to be showing. Try this entirely untested patch...
> 
> The sparc64 version could do with something similar, too.
> 

I'm on sparc64 (pure 64bit) so I can't test your patch. For reference,
I used this (not as smart as yours) patch:

diff -Naur linux-2.6.18.1/include/asm-sparc64/elf.h linux-2.6.18.1-fix/include/asm-sparc64/elf.h
--- linux-2.6.18.1/include/asm-sparc64/elf.h    2006-09-20 03:42:06.000000000 +0000
+++ linux-2.6.18.1-fix/include/asm-sparc64/elf.h        2006-10-19 08:57:11.000000000 +0000
@@ -142,6 +142,7 @@
 #define ELF_ET_DYN_BASE         0x0000010000000000UL
 #endif

+#ifdef __KERNEL__

 /* This yields a mask that user programs can use to figure out what
    instruction set this cpu supports.  */
@@ -163,6 +164,8 @@

 #define ELF_HWCAP      sparc64_elf_hwcap();

+#endif
+
 /* This yields a string that ld.so will use to load implementation
    specific libraries for optimization.  This is more specific in
    intent than poking at uname or /proc/cpuinfo.  */



Andrew Walrond
-
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/