On 1 October 2018 at 22:25, Heiko Carstens <heiko.carst...@de.ibm.com> wrote:
> On Sun, Sep 30, 2018 at 06:49:50PM +0200, Ard Biesheuvel wrote:
>> Commit e872267b8bcbb179 ("jump_table: move entries into ro_after_init
>> region") moved the __jump_table input section into the __ro_after_init
>> output section, but inadvertently put the macro in the wrong place in
>> the s390 linker script. Let's fix that.
>>
>> Fixes: e872267b8bcbb179 ("jump_table: move entries into ro_after_init
>> region")
>> Reported-by: Guenter Roeck <li...@roeck-us.net>
>> Cc: Heiko Carstens <heiko.carst...@de.ibm.com>
>> Cc: Kees Cook <keesc...@chromium.org>
>> Cc: Thomas Gleixner <t...@linutronix.de>
>> Cc: Ingo Molnar <mi...@redhat.com>
>> Cc: Martin Schwidefsky <schwidef...@de.ibm.com>
>> Cc: Jessica Yu <j...@kernel.org>
>> Cc: Peter Zijlstra <pet...@infradead.org>
>> Signed-off-by: Ard Biesheuvel <ard.biesheu...@linaro.org>
>> ---
>> arch/s390/kernel/vmlinux.lds.S | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Acked-by: Heiko Carstens <heiko.carst...@de.ibm.com>
>
> I don't think this is very obvious, but this fixes current build breakage
> in linux-next and I assume Thomas should pick this up.
>
Indeed.
Thomas, Ingo,
Could you please take this fix for the jump lable changes queued in
-next, and the other one I sent out yesterday [0], through core/core
in tip.git as before?
Thanks,
Ard.
[0]
https://lore.kernel.org/lkml/20181001081324.11553-1-ard.biesheu...@linaro.org/
