On 5/17/2025 1:38 AM, Tim Harvey wrote:
Incidentally, while looking at this I noticed if you enable CONFIG_FORTIFY_SOURCE you'll get a splat from the memcpy in function you added in your patch: [ 161.608607] ------------[ cut here ]------------ [ 161.608646] memcpy: detected field-spanning write (size 104) of single field "&mgmt_frame->u" at drivers/net/wir eless/broadcom/brcm80211/brcmfmac/cyw/core.c:307 (size 26) [ 161.608712] WARNING: CPU: 1 PID: 64 at drivers/net/wireless/broadcom/brcm80211/brcmfmac/cyw/core.c:307 brcmf_not ify_auth_frame_rx+0x1f4/0x210 [ 161.647854] CPU: 1 UID: 0 PID: 64 Comm: kworker/1:2 Not tainted 6.15.0-rc5-01256-g68b44b05f4c8 #153 PREEMPT [ 161.657699] Hardware name: Gateworks Venice GW73xx-0x i.MX8MM Development Kit (DT) [ 161.665279] Workqueue: events brcmf_fweh_event_worker [ 161.670348] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 161.677322] pc : brcmf_notify_auth_frame_rx+0x1f4/0x210 [ 161.682557] lr : brcmf_notify_auth_frame_rx+0x1f4/0x210 [ 161.687789] sp : ffff80008065bc30 [ 161.691107] x29: ffff80008065bc30 x28: ffffabb0a8e7d270 x27: ffff1f01c0b0c8c0 [ 161.698269] x26: dead000000000100 x25: dead000000000122 x24: ffff80008065bd58 [ 161.705426] x23: ffff1f01c03bc008 x22: ffff1f01c114b750 x21: 0000000000000080 [ 161.712587] x20: 0000000000000068 x19: ffff1f01c02c7f80 x18: 0000000000000030 [ 161.719744] x17: 0000000000000000 x16: 0000000000000000 x15: 00000000ffffffff [ 161.726903] x14: 000000000000000d x13: 7720676e696e6e61 x12: 00000000ffffffea [ 161.734062] x11: ffff80008065b9f8 x10: ffffabb0a93242c0 x9 : 0000000000000001 [ 161.741220] x8 : 0000000000000001 x7 : c0000000ffffefff x6 : 0000000000017fe8 [ 161.748376] x5 : ffff1f01ff775808 x4 : 0000000000000000 x3 : 0000000000000027 [ 161.755536] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff1f01c028a080 [ 161.762696] Call trace: [ 161.765151] brcmf_notify_auth_frame_rx+0x1f4/0x210 (P) [ 161.770391] brcmf_fweh_call_event_handler+0x40/0xc0 [ 161.775368] brcmf_fweh_event_worker+0x158/0x3b8 [ 161.779999] process_one_work+0x16c/0x2bc [ 161.784024] worker_thread+0x2dc/0x3dc [ 161.787784] kthread+0x130/0x200 [ 161.791028] ret_from_fork+0x10/0x20 [ 161.794618] ---[ end trace 0000000000000000 ]--- Maybe you can submit a patch for that.
Okay. I do not run with that Kconfig option. Will have to look into how to fix this. Probably need some kind of annotation. If you know what is needed feel free to post a patch for it.
Thanks, Arend
