From: Johannes Berg <johannes@sipsolutions.net>
To: Kees Cook <keescook@chromium.org>, Jouni Malinen <j@w1.fi>
Cc: Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Allen Pais <allen.lkml@gmail.com>,
Romain Perier <romain.perier@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Vaibhav Gupta <vaibhavgupta40@gmail.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] intersil: Use struct_group() for memcpy() region
Date: Thu, 18 Nov 2021 20:46:11 +0100 [thread overview]
Message-ID: <c5d8c214b5df75b5b77450d71c7aec9f3bd97a67.camel@sipsolutions.net> (raw)
In-Reply-To: <20211118184158.1284180-1-keescook@chromium.org>
On Thu, 2021-11-18 at 10:41 -0800, Kees Cook wrote:
>
> /* 802.11 */
> - __le16 frame_control; /* parts not used */
> - __le16 duration_id;
> - u8 addr1[ETH_ALEN];
> - u8 addr2[ETH_ALEN]; /* filled by firmware */
> - u8 addr3[ETH_ALEN];
> - __le16 seq_ctrl; /* filled by firmware */
> + struct_group(frame,
Arguably, that should be 'header' rather than 'frame' :)
johannes
next prev parent reply other threads:[~2021-11-18 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 18:41 [PATCH] intersil: Use struct_group() for memcpy() region Kees Cook
2021-11-18 19:46 ` Johannes Berg [this message]
2021-11-18 20:25 ` Kees Cook
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=c5d8c214b5df75b5b77450d71c7aec9f3bd97a67.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=allen.lkml@gmail.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=j@w1.fi \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romain.perier@gmail.com \
--cc=vaibhavgupta40@gmail.com \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).