From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Alexandru Hossu <hossu.alexandru@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
luka.gejak@linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] staging: rtl8723bs: fix OOB write in HT_caps_handler()
Date: Mon, 27 Apr 2026 05:11:19 -0600 [thread overview]
Message-ID: <2026042737-riding-bunkhouse-f8e0@gregkh> (raw)
In-Reply-To: <ae8w9tkpM8G2NWWM@stanley.mountain>
On Mon, Apr 27, 2026 at 12:48:38PM +0300, Dan Carpenter wrote:
> On Mon, Apr 27, 2026 at 02:28:39AM -0700, Alexandru Hossu wrote:
> > On Mon, Apr 27, 2026 at 11:17 AM, Dan Carpenter wrote:
> > > We need a little change log here. I was hoping you would provide
> > > a link to the AI review in the changelog.
> >
> > Hi Dan,
> >
> > Sorry about the missing changelog, will add it in v3.
> >
> > For the AI review link, I don't have a direct link to the bot output.
> > What I know is from Greg's reply in the v1 thread on lore.kernel.org,
>
> What about a link to the email on lore?
Sorry, I was on a plane with no connectivity to look it up, here's the
AI review for my patch:
https://sashiko.dev/#/patchset/2026041408-grill-mahogany-d1e3%40gregkh
> > where he said both his fix and mine would break things on some systems
> > according to the review bot and asked me to use truncation instead.
> > I went with min_t() specifically because he asked for it.
> >
> > You're right that technically early return would have been strictly
> > better than the original, the original was already writing out of
> > bounds so it wasn't working to begin with. But since Greg asked for
> > truncation I kept it that way.
>
> This is the path of least resistance, but it's better to push back
> on bad advice from AI. Greg won't be offended. And if he still
> doesn't like after you push back then you can still do the min_t()
> version. Both versions are fine really, but I generally go with
> the stricter one when it doesn't break anything that wasn't already
> very broken.
Agreed, it takes a lot to offend me these days :)
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-27 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 8:17 [PATCH v2 0/2] staging: rtl8723bs: fix OOB write in HT_caps_handler and OOB read in OnAssocRsp Alexandru Hossu
2026-04-27 8:17 ` [PATCH v2 1/2] staging: rtl8723bs: fix OOB write in HT_caps_handler() Alexandru Hossu
2026-04-27 9:17 ` Dan Carpenter
2026-04-27 9:28 ` Alexandru Hossu
2026-04-27 9:48 ` Dan Carpenter
2026-04-27 11:11 ` Greg KH [this message]
2026-04-27 12:58 ` Dan Carpenter
2026-04-27 13:11 ` Greg KH
2026-04-27 14:32 ` Luka Gejak
2026-04-27 14:45 ` Dan Carpenter
2026-04-27 14:48 ` Dan Carpenter
2026-04-27 8:17 ` [PATCH v2 2/2] staging: rtl8723bs: fix OOB read in OnAssocRsp() IE loop 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=2026042737-riding-bunkhouse-f8e0@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 \
--cc=stable@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