Re: next: WARNING: CPU: 0 PID: 1200 at mm/page_alloc.c:4744 __alloc_pages+0x2e8/0x3a0

[Geert Uytterhoeven <geert@linux-m68k.org>]

On Sat, May 13, 2023 at 10:54 AM Dan Carpenter <dan.carpenter@linaro.org> wrote:
> On Fri, May 12, 2023 at 01:56:30PM +0000, Chuck Lever III wrote:
> > > On May 12, 2023, at 6:32 AM, Dan Carpenter <dan.carpenter@linaro.org> wrote:
> > > I'm pretty sure Chuck Lever did this intentionally, but he's not on the
> > > CC list.  Let's add him.
> > >
> > > regards,
> > > dan carpenter
> > >
> > > On Fri, May 12, 2023 at 06:15:04PM +0530, Naresh Kamboju wrote:
> > >> Following kernel warning has been noticed on qemu-arm64 while running kunit
> > >> tests while booting Linux 6.4.0-rc1-next-20230512 and It was started from
> > >> 6.3.0-rc7-next-20230420.
> > >>
> > >> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > >>
> > >> This is always reproducible on qemu-arm64, qemu-arm, qemu-x86 and qemu-i386.
> > >> Is this expected warning as a part of kunit tests ?
> >
> > Dan's correct, this Kunit test is supposed to check the
> > behavior of the API when a too-large privsize is specified.
> >
> > I'm not sure how to make this work without the superfluous
> > warning. Would adding GFP_NOWARN to the allocation help?
>
> That would silence the splat, yes.

But introduce a build failure, as GFP_NOWARN does not exist.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds