lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 11 Oct 2022 11:12:56 +0300 From: Kalle Valo <kvalo@...nel.org> To: "Arnd Bergmann" <arnd@...db.de> Cc: "Naresh Kamboju" <naresh.kamboju@...aro.org>, Netdev <netdev@...r.kernel.org>, "open list" <linux-kernel@...r.kernel.org>, linux-wireless@...r.kernel.org, "David S . Miller" <davem@...emloft.net>, "Eric Dumazet" <edumazet@...gle.com>, "Jakub Kicinski" <kuba@...nel.org>, "Paolo Abeni" <pabeni@...hat.com>, ath11k@...ts.infradead.org, regressions@...ts.linux.dev, lkft-triage@...ts.linaro.org Subject: Re: drivers/net/wireless/ath/ath11k/mac.c:2238:29: warning: 'ath11k_peer_assoc_h_he_limit' reading 16 bytes from a region of size 0 "Arnd Bergmann" <arnd@...db.de> writes: > On Mon, Oct 10, 2022, at 6:54 PM, Kalle Valo wrote: >> Naresh Kamboju <naresh.kamboju@...aro.org> writes: > >>> >>> Build log: https://builds.tuxbuild.com/2F4W7nZHNx3T88RB0gaCZ9hBX6c/ >> >> Thanks, I was able to reproduce it now and submitted a patch: >> >> https://patchwork.kernel.org/project/linux-wireless/patch/20221010160638.20152-1-kvalo@kernel.org/ >> >> But it's strange that nobody else (myself included) didn't see this >> earlier. Nor later for that matter, this is the only report I got about >> this. Arnd, any ideas what could cause this only to happen on GCC 11? >> >> -- >> https://patchwork.kernel.org/project/linux-wireless/list/ >> >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches > > No idea here, though I have not tried to reproduce it. This looks > like a false positive to me, which might be the result of some > missed optimization in the compiler when building with certain > options. I see in the .config that KASAN is enabled, and this sometimes > causes odd behavior like this. If it does not happen without KASAN, > maybe report it as a bug against the compiler. You guessed correctly, disabling KASAN makes the warning go away. So no point of reporting this to GCC, thanks for the help! -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists