linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	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: Sun, 25 Jun 2023 15:16:54 +0000	[thread overview]
Message-ID: <206F3FDB-59BE-4386-82D2-6FF3CD16D053@oracle.com> (raw)
In-Reply-To: <CAMuHMdW3NO9tafYsCJGStA7YeWye8gwKm2HYb72f1PRXGfXNWg@mail.gmail.com>



> On Jun 25, 2023, at 4:46 AM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> 
> 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.

This is the fix that went in:

commit b21c7ba6d9a5532add3827a3b49f49cbc0cb9779
Author:     Chuck Lever <chuck.lever@oracle.com>
AuthorDate: Fri May 19 13:12:50 2023 -0400
Commit:     Jakub Kicinski <kuba@kernel.org>
CommitDate: Mon May 22 19:24:52 2023 -0700

    net/handshake: Squelch allocation warning during Kunit test

    The "handshake_req_alloc excessive privsize" kunit test is intended
    to check what happens when the maximum privsize is exceeded. The
    WARN_ON_ONCE_GFP at mm/page_alloc.c:4744 can be disabled safely for
    this test.

    Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
    Fixes: 88232ec1ec5e ("net/handshake: Add Kunit tests for the handshake consumer API")
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Link: https://lore.kernel.org/r/168451636052.47152.9600443326570457947.stgit@oracle-102.nfsv4bat.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

diff --git a/net/handshake/handshake-test.c b/net/handshake/handshake-test.c
index e6adc5dec11a..6193e46ee6d9 100644
--- a/net/handshake/handshake-test.c
+++ b/net/handshake/handshake-test.c
@@ -102,7 +102,7 @@ struct handshake_req_alloc_test_param handshake_req_alloc_params[] = {
        {
                .desc                   = "handshake_req_alloc excessive privsize",
                .proto                  = &handshake_req_alloc_proto_6,
-               .gfp                    = GFP_KERNEL,
+               .gfp                    = GFP_KERNEL | __GFP_NOWARN,
                .expect_success         = false,
        },
        {

Is there a platform where __GPF_NOWARN is not defined?


--
Chuck Lever



  reply	other threads:[~2023-06-25 15:17 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
2023-06-25  8:46       ` Geert Uytterhoeven
2023-06-25 15:16         ` Chuck Lever III [this message]
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=206F3FDB-59BE-4386-82D2-6FF3CD16D053@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=dan.carpenter@linaro.org \
    --cc=elver@google.com \
    --cc=geert@linux-m68k.org \
    --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