[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <163818277998.17830.3859485770079586213.kvalo@codeaurora.org>
Date: Mon, 29 Nov 2021 10:46:25 +0000 (UTC)
From: Kalle Valo <kvalo@...eaurora.org>
To: Kees Cook <keescook@...omium.org>
Cc: Lennert Buytenhek <buytenh@...tstofly.org>,
Kees Cook <keescook@...omium.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
wengjianfeng <wengjianfeng@...ong.com>,
Lv Yunlong <lyl2019@...l.ustc.edu.cn>,
Arnd Bergmann <arnd@...db.de>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
Allen Pais <allen.lkml@...il.com>,
Zheyu Ma <zheyuma97@...il.com>, linux-kernel@...r.kernel.org,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH v2] mwl8k: Use named struct for memcpy() region
Kees Cook <keescook@...omium.org> wrote:
> In preparation for FORTIFY_SOURCE performing compile-time and run-time
> field bounds checking for memcpy(), memmove(), and memset(), avoid
> intentionally writing across neighboring fields.
>
> Use named struct in struct mwl8k_cmd_set_key around members key_material,
> tkip_tx_mic_key, and tkip_rx_mic_key so they can be referenced
> together. This will allow memcpy() and sizeof() to more easily reason
> about sizes, improve readability, and avoid future warnings about writing
> beyond the end of key_material.
>
> "pahole" shows no size nor member offset changes to struct
> mwl8k_cmd_set_key. "objdump -d" shows no object code changes.
>
> Signed-off-by: Kees Cook <keescook@...omium.org>
Patch applied to wireless-drivers-next.git, thanks.
f01b3774309f mwl8k: Use named struct for memcpy() region
--
https://patchwork.kernel.org/project/linux-wireless/patch/20211119004905.2348143-1-keescook@chromium.org/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists