From: Guenter Roeck <linux@roeck-us.net>
To: stable <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Build failures in v4.14.y, v4.19.y, v5.0.y, v5.1.y
Date: Mon, 27 May 2019 16:41:51 -0700 [thread overview]
Message-ID: <b68aabcb-eb5a-561d-225c-6ebcf84870d7@roeck-us.net> (raw)
In-Reply-To: <14854627-178c-ed40-d8cf-913035167df8@roeck-us.net>
On 5/27/19 4:39 PM, Guenter Roeck wrote:
> The following build failure affects all stable releases starting with v4.14.y.
> v4.9.y and earlier are not affected.
>
Additional information: v4.14.121, v4.19.45, v5.0.18, and v5.1.4 are not affected.
Guenter
> Guenter
>
> ---
> Build reference: v4.14.122
> gcc version: x86_64-linux-gcc.br_real (Buildroot 2017.02) 6.3.0
>
> Building um:defconfig ... failed
> --------------
> Error log:
> In file included from /opt/buildbot/slave/stable-queue-4.14/build/arch/x86/um/../kernel/module.c:34:0:
> /opt/buildbot/slave/stable-queue-4.14/build/arch/x86/include/asm/text-patching.h: In function ‘int3_emulate_jmp’:
> /opt/buildbot/slave/stable-queue-4.14/build/arch/x86/include/asm/text-patching.h:43:6: error: ‘struct pt_regs’ has no member named ‘ip’
> regs->ip = ip;
> ^~
> /opt/buildbot/slave/stable-queue-4.14/build/arch/x86/include/asm/text-patching.h: In function ‘int3_emulate_push’:
> /opt/buildbot/slave/stable-queue-4.14/build/arch/x86/include/asm/text-patching.h:58:6: error: ‘struct pt_regs’ has no member named ‘sp’
> regs->sp -= sizeof(unsigned long);
> ^~
> /opt/buildbot/slave/stable-queue-4.14/build/arch/x86/include/asm/text-patching.h:59:24: error: ‘struct pt_regs’ has no member named ‘sp’
> *(unsigned long *)regs->sp = val;
> ^~
> /opt/buildbot/slave/stable-queue-4.14/build/arch/x86/include/asm/text-patching.h: In function ‘int3_emulate_call’:
> /opt/buildbot/slave/stable-queue-4.14/build/arch/x86/include/asm/text-patching.h:64:30: error: ‘struct pt_regs’ has no member named ‘ip’
> int3_emulate_push(regs, regs->ip - INT3_INSN_SIZE + CALL_INSN_SIZE);
> ^~
> make[2]: *** [arch/x86/um/../kernel/module.o] Error 1
next prev parent reply other threads:[~2019-05-27 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 23:39 Build failures in v4.14.y, v4.19.y, v5.0.y, v5.1.y Guenter Roeck
2019-05-27 23:41 ` Guenter Roeck [this message]
2019-05-28 4:48 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b68aabcb-eb5a-561d-225c-6ebcf84870d7@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).