linux-kernel - vmlinux ld relocation errors on Alpha

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

Message-ID: <20181024144629.GA6338@gherkin.frus.com>
Date:   Wed, 24 Oct 2018 09:46:29 -0500
From:   Bob Tracy <rct@...rkin.frus.com>
To:     linux-alpha@...r.kernel.org
Cc:     debian-alpha@...ts.debian.org, linux-kernel@...r.kernel.org
Subject: vmlinux ld relocation errors on Alpha

Back in January of 2017, a patch set was created for the 4.9.0 kernel and
*hopefully* sent upstream to address the subject issue.  The patch
implemented a workaround: defining a new "alphalib" section for all the
Alpha-specific library functions to be linked into the final vmlinux.
The patch was definitely not implemented in a vacuum: Helge Deller and
Michael Cree suggested the fix approach, and both Maciej W. Rozycki and
Matt Turner provided significant input along the way.

At this late date, I was forced to resync my Alpha build tree with the
one from "kernel.org", and noticed the patch set never made it into
mainline.  There's a definite possibility it was never submitted
upstream, and a further possibility it was NACK'd for some reason.

Am currently attempting a native 4.19.0 build with an up-to-date debian
"sid" toolchain.  If the build succeeds, than the issue became OBE for
whatever reason.  Otherwise, it would be nice to know what happened to
the patch set.  Should know either way as far as the build in a few more
hours.

--Bob