On Thu, Sep 05, 2019 at 11:15:14AM +0200, Borislav Petkov wrote: > On Wed, Sep 04, 2019 at 04:45:05PM -0500, Steve Wahl wrote: > > The last change to this Makefile caused relocation errors when loading > > a kdump kernel. > > How do those relocation errors look like?
kexec: Overflow in relocation type 11 value 0x11fffd000 ... when loading the crash kernel. > What exactly caused those errors, the flags removal from > kexec-purgatory.o? No, it's the flags for compiling the other objects (purgatory.o, sha256.o, and string.o) that cause the problem. You may have missed the added initial values for PURGATORY_CFLAGS_REMOVE and PURGATORY_CFLAGS. This changes -mcmodel=kernel back to -mcmodel=large, and adds back -ffreestanding and -fno-zero-initialized-in-bss, to match the previous flags. -mcmodel=kernel is the major cause of the relocation errors, as the code generated contained only 32 bit references to things that can be anywhere in 64 bit address space. The remaining flag changes are appropriate for compiling a standalone module, which applies to 3 of the objects compiled from C files in this directory -- they contribute to a standalone piece of code that is not (technically) linked with the rest of the kernel. (Fine line here: the standalone binary does not get any symbols resolved against the rest of the kernel; which is why I say it's not *linked* with it. The binary image of this standalone binary does get put into a character array that is pulled into the kernel object code, so it does become part of the kernel, but just as an array of bytes that kexec copies somewhere and eventually jumps to as a standalone program.) kexec-purgatory.o, on the other hand, does get linked with the rest of the kernel and should be compiled with the usual flags, not standalone flags. That is why changes for it are a bit different, which you noticed. > Can we have the failure properly explained in the commit message pls? Is " 'kexec: Overflow in relocation type 11 value 0x11fffd000' when loading the crash kernel" sufficient, or would you like more? > > This change restores the appropriate flags, without > > You don't have to say "This change" in the commit message - it is > obvious which change you're talking about. Instead say: "Restore the > appropriate... " OK. --> Steve -- Steve Wahl, Hewlett Packard Enterprise
