Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, wireguard@lists.zx2c4.com,
	netdev@vger.kernel.org
Subject: Re: Fw: [Bug 217054] New: wireguard - allowedips.c - warning: the frame size of 1032 bytes is larger than 1024 bytes
Date: Sat, 18 Feb 2023 20:06:18 +0100	[thread overview]
Message-ID: <Y/EhqqFJepo3Ncpr@zx2c4.com> (raw)
In-Reply-To: <20230218095036.7c558146@hermes.local>

On Sat, Feb 18, 2023 at 09:50:36AM -0800, Stephen Hemminger wrote:
> 
> 
> 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

This keeps coming up. The frame size that the compiler targets on 64-bit
is 1280, not 1024. The reporter misconfigured the .config. Maybe there
should be a min value for that. Dunno. Old topic.

Jason

      reply	other threads:[~2023-02-18 19:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18 17:50 Stephen Hemminger
2023-02-18 19:06 ` Jason A. Donenfeld [this message]

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=Y/EhqqFJepo3Ncpr@zx2c4.com \
    --to=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=stephen@networkplumber.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).