From: Johannes Berg <johannes@sipsolutions.net>
To: Tristan Madani <tristmd@gmail.com>, linux-wireless@vger.kernel.org
Cc: error27@gmail.com, kuba@kernel.org, dcbw@redhat.com,
linville@tuxdriver.com, lkp@intel.com
Subject: Re: [PATCH v4 0/2] wifi: libertas: fix two OOB reads from firmware fields
Date: Tue, 05 May 2026 11:52:22 +0200 [thread overview]
Message-ID: <66d038a7793660ed1b4d47b615d09b092a85c84b.camel@sipsolutions.net> (raw)
In-Reply-To: <20260504191452.3408257-1-tristan@talencesecurity.com>
Tristan,
This is going to be the last time I reply to you if you continue this.
Please:
1) Send patches that actually apply to the relevant tree
(wireless or wireless-next in this case, ideally tagging it in the
subject such as "[PATCH wireless v5 1/2]")
2) Consider feedback you get. Even in another driver it's not useful to
check one size against another size if both are provided by the
device, unless the other is already validated. If so, add a comment.
3) Disclose AI/LLM usage per
https://docs.kernel.org/process/coding-assistants.html
(Yes, I don't believe you came out of nowhere without it.)
johannes
prev parent reply other threads:[~2026-05-05 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 19:14 [PATCH v4 0/2] wifi: libertas: fix two OOB reads from firmware fields Tristan Madani
2026-05-04 19:14 ` [PATCH v4 1/2] wifi: libertas: fix OOB read from firmware pkt_ptr offset in RX path Tristan Madani
2026-05-04 19:14 ` [PATCH v4 2/2] wifi: libertas: fix OOB read from firmware bssdescriptsize in scan response Tristan Madani
2026-05-05 9:52 ` Johannes Berg [this message]
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=66d038a7793660ed1b4d47b615d09b092a85c84b.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=error27@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lkp@intel.com \
--cc=tristmd@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