From: Chuck Lever <cel@kernel.org>
To: naresh.kamboju@linaro.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kasan-dev@googlegroups.com, kunit-dev@googlegroups.com,
lkft-triage@lists.linaro.org, elver@google.com,
akpm@linux-foundation.org, mgorman@techsingularity.net,
aryabinin@virtuozzo.com
Subject: [PATCH] net/handshake: Squelch allocation warning during Kunit test
Date: Fri, 12 May 2023 15:02:18 -0400 [thread overview]
Message-ID: <168391812685.21298.13859211358278163731.stgit@91.116.238.104.host.secureserver.net> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
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 allocator call site.
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>
---
net/handshake/request.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/handshake/request.c b/net/handshake/request.c
index d78d41abb3d9..24097cccd158 100644
--- a/net/handshake/request.c
+++ b/net/handshake/request.c
@@ -120,7 +120,8 @@ struct handshake_req *handshake_req_alloc(const struct handshake_proto *proto,
if (!proto->hp_accept || !proto->hp_done)
return NULL;
- req = kzalloc(struct_size(req, hr_priv, proto->hp_privsize), flags);
+ req = kzalloc(struct_size(req, hr_priv, proto->hp_privsize),
+ flags | __GFP_NOWARN);
if (!req)
return NULL;
reply other threads:[~2023-05-12 19:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=168391812685.21298.13859211358278163731.stgit@91.116.238.104.host.secureserver.net \
--to=cel@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.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