From: Tristan Madani <tristmd@gmail.com>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: Doruk Tan Ozturk <doruk@0sec.ai>,
Johannes Berg <johannes@sipsolutions.net>,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, tristan@talencesecurity.com
Subject: Re: [PATCH] wifi: carl9170: clamp command response copy to the read buffer size
Date: Thu, 25 Jun 2026 23:46:03 -0000 [thread overview]
Message-ID: <178243116343.3635355.16109712055530784127@gmail.com> (raw)
In-Reply-To: CAPdMp1oWXvtdvp8D0f32vpvzGa0H9PhprQcACqqoc4Gnyy=f6A@mail.gmail.com
Hi Christian, Doruk,
No worries at all, these things happen. Both patches address the same
underlying issue from different angles -- mine returns early after
carl9170_restart() to skip the invalid response entirely, Doruk's
clamps the memcpy to ar->readlen.
Either approach works. If it helps, I'm happy to respin my 3-patch
series (the other two patches fix the TX status off-by-two and
rx_stream failover overflow in the same driver).
Let me know if you'd prefer a fresh resend or if you'd rather pick
from what's already on the list.
Thanks,
Tristan
next reply other threads:[~2026-06-25 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 23:46 Tristan Madani [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-19 22:48 [PATCH] wifi: carl9170: clamp command response copy to the read buffer size Doruk Tan Ozturk
2026-06-21 8:17 ` Christian Lamparter
2026-06-21 10:24 ` Doruk (0sec)
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=178243116343.3635355.16109712055530784127@gmail.com \
--to=tristmd@gmail.com \
--cc=chunkeey@gmail.com \
--cc=doruk@0sec.ai \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tristan@talencesecurity.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