From: Greg KH <gregkh@linuxfoundation.org>
To: Alexandru Hossu <hossu.alexandru@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
error27@gmail.com, luka.gejak@linux.dev
Subject: Re: [PATCH v3 0/2] staging: rtl8723bs: fix OOB write in HT_caps_handler and OOB read in OnAssocRsp
Date: Mon, 4 May 2026 16:13:38 +0200 [thread overview]
Message-ID: <2026050402-ranch-imprint-1c7c@gregkh> (raw)
In-Reply-To: <20260428091621.739680-1-hossu.alexandru@gmail.com>
On Tue, Apr 28, 2026 at 11:16:19AM +0200, Alexandru Hossu wrote:
> v3, addressing Dan Carpenter's and Luka Gejak's feedback on v2.
>
> Greg, please drop your patch and take this one instead.
What patch should I drop? What is the git id of it?
And what about these review comments:
https://sashiko.dev/#/patchset/20260428091621.739680-1-hossu.alexandru@gmail.com
And have you tested this on real hardware?
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-04 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 9:16 [PATCH v3 0/2] staging: rtl8723bs: fix OOB write in HT_caps_handler and OOB read in OnAssocRsp Alexandru Hossu
2026-04-28 9:16 ` [PATCH v3 1/2] staging: rtl8723bs: fix OOB write in HT_caps_handler() Alexandru Hossu
2026-04-28 10:17 ` Luka Gejak
2026-04-28 9:16 ` [PATCH v3 2/2] staging: rtl8723bs: fix OOB read in OnAssocRsp() IE loop Alexandru Hossu
2026-04-28 10:17 ` Luka Gejak
2026-05-04 14:13 ` Greg KH [this message]
2026-05-05 17:22 ` [PATCH v4 0/2] staging: rtl8723bs: fix OOB write and read in HT_caps_handler and OnAssocRsp Alexandru Hossu
2026-05-05 17:22 ` [PATCH v4 1/2] staging: rtl8723bs: fix OOB write and read in HT_caps_handler() Alexandru Hossu
2026-05-05 17:22 ` [PATCH v4 2/2] staging: rtl8723bs: fix OOB reads in OnAssocRsp() IE parsing Alexandru Hossu
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=2026050402-ranch-imprint-1c7c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=error27@gmail.com \
--cc=hossu.alexandru@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luka.gejak@linux.dev \
/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