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: <20201216030154.GL3579531@ZenIV.linux.org.uk>
Date:   Wed, 16 Dec 2020 03:01:54 +0000
From:   Al Viro <viro@...iv.linux.org.uk>
To:     "Maciej W. Rozycki" <macro@...ux-mips.org>
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 Mon, Dec 07, 2020 at 06:01:43PM +0000, Maciej W. Rozycki wrote:
> On Thu, 3 Dec 2020, Al Viro wrote:
> 
> > > Linux-mips was cc'd, but I'm adding Thomas B to the cc here explicitly
> > > just so that he has a heads-up on this thing and can go and look at
> > > the mailing list in case it goes to a separate mailbox for him..
> > 
> > I would certainly appreciate review and testing - this branch sat
> > around in the "should post it someday" state since June (it was
> > one of the followups grown from regset work back then), and I'm
> > _not_ going to ask pulling it without an explicit OK from mips
> > folks.
> 
>  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?