[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAC_TJvfpeRh322usynr2Ud3KVCd3HaNnviOmdhekXSnC-sq2sA@mail.gmail.com>
Date: Mon, 28 Dec 2020 13:37:13 -0600
From: Kalesh Singh <kaleshsingh@...gle.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Guenter Roeck <linux@...ck-us.net>,
Thomas Gleixner <tglx@...utronix.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 5.11-rc1
On Mon, Dec 28, 2020 at 12:59 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Mon, Dec 28, 2020 at 7:51 AM Guenter Roeck <linux@...ck-us.net> wrote:
> >
> > Build results:
> > total: 153 pass: 151 fail: 2
>
> Thanks for doing these for the mainline rc's too. I've seen them for
> the stable kernels, but it's lovely to see it for rc1.
>
> > ERROR: modpost: "irq_check_status_bit" [drivers/perf/arm_spe_pmu.ko] undefined!
> >
> > Caused by: fdd029630434 ("genirq: Move status flag checks to core")
>
> Ahh. Does it just need a
>
> EXPORT_SYMBOL_GPL(irq_check_status_bit);
>
> in there? Because it looks like at least irq_is_percpu() and
> irq_is_percpu_devid() are used in drivers/perf/ and can apparently be
> modules.
>
> Thomas?
>
> > ia64:defconfig:
> >
> > include/linux/mmzone.h:1156:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE
> >
> > and various related warnings.
> >
> > Caused by: 214496cb1870 ("ia64: make SPARSEMEM default and disable DISCONTIGMEM")
> >
> > Fix submitted ("ia64: fix build failure caused by memory model changes").
>
> Ok, I won't worry about that one.
>
> > qemu boot tests:
> >
> > arm:raspi2 hangs during boot.
> >
> > Caused by: ffdad793d579 ("irqchip/bcm2836: Make IPIs use handle_percpu_devid_irq()")
> >
> > Fix submitted ("irqchip/bcm2836: Fix IPI acknowledgement after conversion to
> > handle_percpu_devid_irq").
>
> Same.
>
> > parisc: Failed to execute /sbin/init (error -12)
> >
> > Caused by: c49dd3401802 ("mm: speedup mremap on 1GB or larger regions")
>
> Looks like Kalesh is looking at it.
>
> I don't think that was supposed to matter at all on parisc, but
> clearly something bad happened.
>
> parsic doesn't even enable HAVE_MOVE_PMD, much less the new
> HAVE_MOVE_PUD. Strange.
Hi Linus,
I had sent the fix for this issue which was taken into the -mm tree by
Andrew. (https://ozlabs.org/~akpm/mmotm/broken-out/mm-mremap-fix-extent-calculation.patch)
Please, let me know if there is anything else needed on my end.
Thanks,
Kalesh
>
> Linus
Powered by blists - more mailing lists