linux-kernel - Re: [PATCH 6/8] MIPS: ELF: Interpret the NAN2008 file header flag

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]

Message-ID: <alpine.DEB.2.00.1511251713340.16168@tp.orcam.me.uk>
Date:	Wed, 25 Nov 2015 17:43:39 +0000
From:	"Maciej W. Rozycki" <macro@...tec.com>
To:	Ralf Baechle <ralf@...ux-mips.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Matthew Fortune <Matthew.Fortune@...tec.com>,
	<linux-mips@...ux-mips.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 6/8] MIPS: ELF: Interpret the NAN2008 file header flag

On Fri, 13 Nov 2015, Maciej W. Rozycki wrote:

> This change relies on <https://patchwork.kernel.org/patch/7491081/> to 
> work correctly for dynamic binaries, otherwise an opposite-mode 
> interpreter will be incorrectly accepted, and worse yet enforce any 
> additional shared binaries to have their NaN mode opposite to that of the 
> main binary.  This will normally only happen for broken installations or 
> incorrectly built binaries where PT_INTERP points to the wrong dynamic 
> linker though.  Static binaries are unaffected.

 Ralf, I see that patch has now been applied, commit b582ef5c, and no 
concerns have been raised as to the changes considered here so you can 
give this series a go-ahead at your earliest convenience.  Unless someone 
chimes in at the last minute, that is.

 I'll be rather happy if you can push it through in time for 4.4 so that a 
corresponding change required for glibc to define the earliest Linux 
version to enable 2008-NaN support from can make it to the 2.23 release, 
scheduled for late Jan to early Feb 2016 according to the usual practice 
(see <http://www.gnu.org/software/libc/libc.html> for the release 
timeline).  A slushy freeze period is likely to start from Jan 1st for the 
glibc code base, but a change to set the minimum Linux version only for a 
feature already included is surely going to be acceptable even then.

  Maciej
--
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/