From: Kalle Valo <kvalo@kernel.org>
To: ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v6.1] wifi: ath11k: mac: fix reading 16 bytes from a region of size 0 warning
Date: Tue, 11 Oct 2022 11:15:36 +0300 [thread overview]
Message-ID: <87pmeyojx3.fsf@kernel.org> (raw)
In-Reply-To: <20221010160638.20152-1-kvalo@kernel.org> (Kalle Valo's message of "Mon, 10 Oct 2022 19:06:38 +0300")
Kalle Valo <kvalo@kernel.org> writes:
> From: Kalle Valo <quic_kvalo@quicinc.com>
>
> Linaro reported stringop-overread warnings in ath11k (this is one of many):
>
> drivers/net/wireless/ath/ath11k/mac.c:2238:29: error: 'ath11k_peer_assoc_h_he_limit' reading 16 bytes from a region of size 0 [-Werror=stringop-overread]
>
> My further investigation showed that these warnings happen on GCC 11.3 but not
> with GCC 12.2, and with only the kernel config Linaro provided:
>
> https://builds.tuxbuild.com/2F4W7nZHNx3T88RB0gaCZ9hBX6c/config
>
> I saw the same warnings both with arm64 and x86_64 builds but couldn't figure
> out what exactly triggers the warnings, or why I didn't see them earlier.
> Nobody else has reported this either. This is also why I can't provide a Fixes
> tag as I don't know what's causing this. The function hasn't been touched for
> a year.
Thanks to Arnd I found out that KASAN caused this so I'll update the
commit log in this regard.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-10-11 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 16:06 [PATCH v6.1] wifi: ath11k: mac: fix reading 16 bytes from a region of size 0 warning Kalle Valo
2022-10-11 8:15 ` Kalle Valo [this message]
2022-10-11 8:47 ` [v6.1] " Kalle Valo
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=87pmeyojx3.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
/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).