From: Dan Carpenter <dan.carpenter@linaro.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
kasan-dev <kasan-dev@googlegroups.com>,
"kunit-dev@googlegroups.com" <kunit-dev@googlegroups.com>,
"lkft-triage@lists.linaro.org" <lkft-triage@lists.linaro.org>,
Marco Elver <elver@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@techsingularity.net>,
Andrey Ryabinin <aryabinin@virtuozzo.com>
Subject: Re: next: WARNING: CPU: 0 PID: 1200 at mm/page_alloc.c:4744 __alloc_pages+0x2e8/0x3a0
Date: Fri, 12 May 2023 17:01:31 +0300 [thread overview]
Message-ID: <1059342c-f45a-4065-b088-f7a61833096e@kili.mountain> (raw)
In-Reply-To: <DC7CFF65-F4A2-4481-AA5C-0FA986BE48B7@oracle.com>
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.
regards,
dan carpenter
next prev parent reply other threads:[~2023-05-13 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 12:45 Naresh Kamboju
2023-05-12 13:32 ` Dan Carpenter
2023-05-12 13:56 ` Chuck Lever III
2023-05-12 14:01 ` Dan Carpenter [this message]
2023-06-25 8:46 ` Geert Uytterhoeven
2023-06-25 15:16 ` Chuck Lever III
2023-06-25 15:34 ` Geert Uytterhoeven
2023-05-12 16:17 ` Mike Rapoport
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=1059342c-f45a-4065-b088-f7a61833096e@kili.mountain \
--to=dan.carpenter@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=chuck.lever@oracle.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mgorman@techsingularity.net \
--cc=naresh.kamboju@linaro.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