From: Kalle Valo <kvalo@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] hostap: Add __counted_by for struct prism2_download_data and use struct_size()
Date: Tue, 10 Oct 2023 09:17:34 +0300 [thread overview]
Message-ID: <877cnv57cx.fsf@kernel.org> (raw)
In-Reply-To: <202310091341.74A2D82BB@keescook> (Kees Cook's message of "Mon, 9 Oct 2023 13:42:12 -0700")
Kees Cook <keescook@chromium.org> writes:
>> > Should this be considered a v2 of:
>> > https://lore.kernel.org/linux-hardening/94848cc3-6f5c-46d7-8cc7-98a4f10865b3@embeddedor.com/
>> >
>> > ?
>>
>> Oops... sorry, I forgot I had reviewed this patch of yours.
>>
>> >
>> > Yours is more complete since it includes the struct_size() change...
>> >
>>
>> Should I resend this explicitly marking it as a v2?
>
> I defer to Kalle -- your Subject is more accurate, so perhaps let's just
> let this stand?
No need to resend. I marked Kees' version as Superseded so that I don't
accidentally take the wrong version.
In the title "wifi:" is missing but I can add that during commit.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-10-10 6:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 19:41 [PATCH][next] hostap: Add __counted_by for struct prism2_download_data and use struct_size() Gustavo A. R. Silva
2023-10-09 19:54 ` Kees Cook
2023-10-09 20:33 ` Gustavo A. R. Silva
2023-10-09 20:42 ` Kees Cook
2023-10-10 6:17 ` Kalle Valo [this message]
2023-10-10 12:44 ` Gustavo A. R. Silva
2023-10-10 22:50 ` Kees Cook
2023-10-10 23:24 ` Gustavo A. R. Silva
2023-10-11 9:20 ` [next] wifi: " 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=877cnv57cx.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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