linux-kernel - Re: [PATCHSET] saner elf compat

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

Message-ID: <alpine.LFD.2.21.2012160924010.2104409@eddie.linux-mips.org>
Date:   Wed, 16 Dec 2020 09:44:53 +0000 (GMT)
From:   "Maciej W. Rozycki" <macro@...ux-mips.org>
To:     Al Viro <viro@...iv.linux.org.uk>
cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        the arch/x86 maintainers <x86@...nel.org>,
        linux-mips@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCHSET] saner elf compat

On Wed, 16 Dec 2020, Al Viro wrote:

> >  It may be worth pushing through GDB's gdb.threads/tls-core.exp test case, 
> > making sure no UNSUPPORTED results have been produced due to resource 
> > limits preventing a core from being dumped (and no FAILs, of course), with 
> > o32/n32 native GDB.  This should guarantee our output is still as expected 
> > by an interpreter.  Sadly I'm currently not set up for such testing though 
> > eventually I mean to.
> 
> Umm...  What triple does one use for n32 gdb?

 I don't think there's a standardised one, just configure with CC/CXX set 
for n32 compilation, e.g.:

$ /path/to/configure CC="gcc -mabi=n32" CXX="g++ -mabi=n32"

(and any other options set as usually).  This has to be with CC/CXX rather 
than CFLAGS/CXXFLAGS so that it is guaranteed to be never overridden with 
any logic that might do any fiddling with compilation options.  This will 
set up the test suite accordingly.

 NB this may already be the compiler's default, depending on how it was 
configured, i.e. if `--with-abi=n32' was used, in which case no extra 
options will be required.  I don't know if any standard MIPS distribution 
does it though; 64-bit MIPS/Debian might.  This will be reported with `gcc 
--help -v', somewhere along the way.

 Let me know if there are issues with this approach.

  Maciej