From: Stephen Hemminger <stephen@networkplumber.org>
To: Jason@zx2c4.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Cc: wireguard@lists.zx2c4.com, netdev@vger.kernel.org
Subject: Fw: [Bug 217054] New: wireguard - allowedips.c - warning: the frame size of 1032 bytes is larger than 1024 bytes
Date: Sat, 18 Feb 2023 09:50:36 -0800 [thread overview]
Message-ID: <20230218095036.7c558146@hermes.local> (raw)
Begin forwarded message:
Date: Sat, 18 Feb 2023 15:49:26 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 217054] New: wireguard - allowedips.c - warning: the frame size of 1032 bytes is larger than 1024 bytes
https://bugzilla.kernel.org/show_bug.cgi?id=217054
Bug ID: 217054
Summary: wireguard - allowedips.c - warning: the frame size of
1032 bytes is larger than 1024 bytes
Product: Networking
Version: 2.5
Kernel Version: 6.1.12
Hardware: AMD
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: ionut_n2001@yahoo.com
Regression: No
CC [M] drivers/memstick/core/memstick.o
drivers/net/wireguard/allowedips.c: In function 'root_remove_peer_lists':
drivers/net/wireguard/allowedips.c:80:1: warning: the frame size of 1032 bytes
is larger than 1024 bytes [-Wframe-larger-than=]
80 | }
| ^
drivers/net/wireguard/allowedips.c: In function 'root_free_rcu':
drivers/net/wireguard/allowedips.c:67:1: warning: the frame size of 1032 bytes
is larger than 1024 bytes [-Wframe-larger-than=]
67 | }
| ^
CC [M] drivers/net/wireguard/ratelimiter.o
CC [M] drivers/memstick/core/ms_block.o
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-02-18 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 17:50 Stephen Hemminger [this message]
2023-02-18 19:06 ` Fw: [Bug 217054] New: wireguard - allowedips.c - warning: the frame size of 1032 bytes is larger than 1024 bytes Jason A. Donenfeld
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=20230218095036.7c558146@hermes.local \
--to=stephen@networkplumber.org \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wireguard@lists.zx2c4.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.