From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Tim Harvey <tharvey@gateworks.com>
Cc: brcm80211@lists.linux.dev,
linux-wireless <linux-wireless@vger.kernel.org>,
hostap@lists.infradead.org
Subject: Re: [PATCH wireless-next v3 0/4] wifi: brcmfmac: external auth support for Infineon devices
Date: Sun, 25 May 2025 20:17:12 +0200 [thread overview]
Message-ID: <9bccdc60-7c4f-42f8-b470-86fac4842115@broadcom.com> (raw)
In-Reply-To: <66ab4bd4e87b20004f7acd751674b0b9712164ca.camel@sipsolutions.net>
On 5/25/2025 2:24 PM, Johannes Berg wrote:
> On Sun, 2025-05-25 at 11:47 +0200, Arend van Spriel wrote:
>>
>>> [ 161.608607] ------------[ cut here ]------------
>>> [ 161.608646] memcpy: detected field-spanning write (size 104) of
>>> single field "&mgmt_frame->u" at drivers/net/wireless/broadcom/brcm80211/brcmfmac/cyw/core.c:307 (size 26)
>>
>> 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.
>
> I think just copy to mgmt_frame->u.body instead of ->u itself.
My gutt feeling was telling me the same when I was looking at it
earlier. Thanks for the confirmation although your phrasing seems
cautious ;-)
Regards,
Arend
next prev parent reply other threads:[~2025-05-25 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 0:38 [PATCH wireless-next v3 0/4] wifi: brcmfmac: external auth support for Infineon devices Tim Harvey
2025-05-16 5:27 ` Arend Van Spriel
2025-05-16 23:38 ` Tim Harvey
2025-05-25 9:46 ` Arend van Spriel
2025-05-25 9:47 ` Arend van Spriel
2025-05-25 12:24 ` Johannes Berg
2025-05-25 18:17 ` Arend van Spriel [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-25 8:55 Arend van Spriel
2025-04-28 14:52 ` Peter Robinson
2025-04-29 4:11 ` Arend Van Spriel
2025-04-29 8:18 ` Peter Robinson
2025-04-29 8:55 ` Arend Van Spriel
2025-04-29 10:32 ` Arend van Spriel
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=9bccdc60-7c4f-42f8-b470-86fac4842115@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=hostap@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tharvey@gateworks.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