Bug 217054 - wireguard - allowedips.c - warning: the frame size of 1032 bytes is larger than 1024 bytes
Summary: wireguard - allowedips.c - warning: the frame size of 1032 bytes is larger th...
Status: NEW
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: AMD Linux
: P1 normal
Assignee: Stephen Hemminger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-18 15:49 UTC by sander44
Modified: 2024-01-27 14:42 UTC (History)
1 user (show)

See Also:
Kernel Version: 6.1.12
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description sander44 2023-02-18 15:49:26 UTC
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
Comment 1 Michael Englehorn 2023-07-01 13:46:25 UTC
arch/um/configs/x86_64_defconfig defines CONFIG_FRAME_WARN to 1024. A Wireguard self test at tools/testing/selftests/wireguard/qemu/arch/x86_64.config expects CONFIG_FRAME_WARN to be 1280.

A discussion on the netdev mailing list reports:
"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."

If that's the case, shouldn't the x86_64_defconfig set CONFIG_FRAME_WARN to 1280?
Comment 2 sander44 2024-01-27 14:42:22 UTC
Hi Michael,

So the value should be CONFIG_FRAME_WARN=1280 now?

I had it set to 1024 in the initial configuration file.

Note You need to log in before you can comment on or make changes to this bug.