Commit 923d48e4 authored by Alexander Gordeev's avatar Alexander Gordeev Committed by Heiko Carstens
Browse files

s390/boot: do not check for zero-termination relocation entry 



The relocation table is not expected to contain a zero-termination
entry. The existing check is likely a left-over from similar x86
code that uses zero-entries as delimiters. s390 does not have ones
and therefore the check could be avoided.

Suggested-by: default avatarIlya Leoshkevich <iii@linux.ibm.com>
Acked-by: default avatarSumanth Korikkar <sumanthk@linux.ibm.com>
Acked-by: default avatarHeiko Carstens <hca@linux.ibm.com>
Signed-off-by: default avatarAlexander Gordeev <agordeev@linux.ibm.com>
Signed-off-by: default avatarHeiko Carstens <hca@linux.ibm.com>
parent 4394a507

arch/s390/boot/startup.c

+1 −3
Original line number Diff line number Diff line
@@ -200,9 +200,7 @@ static void kaslr_adjust_relocs(unsigned long min_addr, unsigned long max_addr, 
	long loc;



	/* Adjust R_390_64 relocations */

	for (reloc = vmlinux_relocs_64_start;

		reloc < vmlinux_relocs_64_end && *reloc;

		reloc++) {

	for (reloc = vmlinux_relocs_64_start; reloc < vmlinux_relocs_64_end; reloc++) {

		loc = (long)*reloc + offset;

		if (loc < min_addr || loc > max_addr)

			error("64-bit relocation outside of kernel!\n");