[lkml]   [2020]   [Jan]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v3] x86/vmlinux: Fix with pre-2.23 binutils
On January 14, 2020 8:51:35 AM PST, Borislav Petkov <> wrote:
>On Mon, Jan 13, 2020 at 05:53:32PM -0800, Kees Cook wrote:
>> NAK: linkers can add things at the end of .text that will go missing
>> the kernel if _etext isn't _outside_ the .text section, truly beyond
>> end of the .text section. This patch will break Control Flow
>> checking since the jump tables are at the end of .text.
>Err, which linkers are those? Please elaborate.
>In any case, after reading the thread, I can't help but favor the idea
>of us bumping min binutils version to 2.23.
>Michael (on Cc) says that the 2.21 was kinda broken wrt to the symbols
>fun outside of sections, 2.22 tried to fix it, see
>fd952815307f ("x86-32, relocs: Whitelist more symbols for ld bug
>which Arvind pointed out and 2.23 fixed it for real.
>Now, 2.23 is still very ancient. I'm looking at our releases: openSUSE
>12.1 has the minimum supported gcc version 4.6 by the kernel and
>also the minimum binutils version 2.21 which we support according to
>Now, openSUSE 12.1 is ancient and we ourselves advise people to update
>to current distros so I don't think anyone would still run it.
>So, considering that upping the binutils version would save us from all
>this trouble I say we try it after 5.5 releases for a maximum time of a
>full 5.6 release cycle and see who complains.
>Considering how no one triggered this yet until Arvind, I think no one
>would complain. But I might be wrong.
>So what do people think? hpa?

I'm all for dumping support for an ancient, known buggy binutils.
Sent from my Android device with K-9 Mail. Please excuse my brevity.

 \ /
  Last update: 2020-01-14 22:51    [W:0.078 / U:0.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site