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
| ||
|
Date: Tue, 24 Mar 2020 09:37:13 -0700 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Borislav Petkov <bp@...en8.de> Cc: "Jason A. Donenfeld" <Jason@...c4.com>, Masahiro Yamada <masahiroy@...nel.org>, Kees Cook <keescook@...omium.org>, Arvind Sankar <nivedita@...m.mit.edu>, "H. Peter Anvin" <hpa@...or.com>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, X86 ML <x86@...nel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Thomas Lendacky <Thomas.Lendacky@....com>, Mauro Rossi <issor.oruam@...il.com>, Michael Matz <matz@...e.de> Subject: Re: [PATCH] Documentation/changes: Raise minimum supported binutils version to 2.23 On Tue, Mar 24, 2020 at 9:28 AM Borislav Petkov <bp@...en8.de> wrote: > > Are you or Kees going to deal with any fallout from upping the binutils > version, rushed in in the last week before the merge window? I think it's ok. It's not going to cause any _subtle_ failures, it's going to cause very clear "oh, now it doesn't build" errors. No? And binutils 2.23 is what, 7+ years old by now and apparently had known failure cases too. But if there are silent and subtle failures, that might be a reason to be careful. Are there? Linus
Powered by blists - more mailing lists