From: Guenter Roeck <linux@roeck-us.net>
To: Sasha Levin <sashal@kernel.org>, Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: build failures in v4.4.y stable queue
Date: Wed, 4 Nov 2020 18:34:50 -0800 [thread overview]
Message-ID: <1fc37180-ad6f-d2b7-7921-77e9c271ebb0@roeck-us.net> (raw)
In-Reply-To: <20201104161817.GG2092@sasha-vm>
On 11/4/20 8:18 AM, Sasha Levin wrote:
> On Wed, Nov 04, 2020 at 03:37:09PM +0100, Greg KH wrote:
>> On Wed, Nov 04, 2020 at 06:12:30AM -0800, Guenter Roeck wrote:
>>> Building ia64:defconfig ... failed
>>> --------------
>>> Error log:
>>> drivers/acpi/numa.c: In function 'pxm_to_node':
>>> drivers/acpi/numa.c:49:43: error: 'numa_off' undeclared
>>
>> Caused by 8a3decac087a ("ACPI: Add out of bounds and numa_off
>> protections to pxm_to_node()"), I'll go drop it.
>>
>> Sasha, you didn't queue this up to 4.9, but you did to 4.4?
>>
>>>
>>> Building powerpc:defconfig ... failed
>>> --------------
>>> Error log:
>>> arch/powerpc/kvm/book3s_hv.c: In function ‘kvm_arch_vm_ioctl_hv’:
>>> arch/powerpc/kvm/book3s_hv.c:3161:7: error: implicit declaration of function ‘kvmhv_on_pseries’
>>
>> Caused by 05e6295dc7de ("KVM: PPC: Book3S HV: Do not allocate HPT for a
>> nested guest"), I'll go drop this.
>>
>> Sasha, why did you only queue this up to 4.4 and 5.4 and 5.9 and not the
>> middle queues as well?
>
> Originally it got queued everywhere, but then it looks like I dropped it
> from 4.9-4.19 because of build failures, but it seems that the 4.4
> failure wasn't detected.
>
> Looking into why, it seems that my baseline for that build also fails
> for some reason:
>
> ../../../../linux/arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
> ../../../../linux/arch/powerpc/kernel/exceptions-64s.S:1603: Warning: invalid register expression
> ../../../../linux/arch/powerpc/kernel/exceptions-64s.S:1644: Warning: invalid register expression
> ../../../../linux/arch/powerpc/kernel/exceptions-64s.S:839: Error: attempt to move .org backwards
> ../../../../linux/arch/powerpc/kernel/exceptions-64s.S:840: Error: attempt to move .org backwards
> ../../../../linux/arch/powerpc/kernel/exceptions-64s.S:864: Error: attempt to move .org backwards
> ../../../../linux/arch/powerpc/kernel/exceptions-64s.S:865: Error: attempt to move .org backwards
> make[2]: *** [/home/sasha/data/linux/scripts/Makefile.build:375: arch/powerpc/kernel/head_64.o] Error 1
> make[1]: *** [/home/sasha/data/linux/Makefile:1006: arch/powerpc/kernel] Error 2
>
> I think that I'll rebuild my toolchain for powerpc and redo the baseline
> builds, sorry about that.
>
Is that an allmodconfig build ? That simply won't build in 4.4.y because
exceptions-64s.S is too large there.
Guenter
next prev parent reply other threads:[~2020-11-05 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 14:12 build failures in v4.4.y stable queue Guenter Roeck
2020-11-04 14:37 ` Greg KH
2020-11-04 16:18 ` Sasha Levin
2020-11-05 2:34 ` Guenter Roeck [this message]
2020-11-09 0:19 ` Sasha Levin
2020-11-09 0:47 ` Guenter Roeck
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=1fc37180-ad6f-d2b7-7921-77e9c271ebb0@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.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).