Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Masashi Honma <masashi.honma@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] Fix overread in PREQ frame processing
Date: Mon, 11 May 2026 11:01:39 +0200	[thread overview]
Message-ID: <725b56f42b5fec58196e4055bccb74236145986b.camel@sipsolutions.net> (raw)
In-Reply-To: <CAFk-A4mD=tKHMp8qqAvrsFZjmJHsA1sBe9Wmmn=qEacNMxTH_A@mail.gmail.com> (sfid-20260511_105817_539632_BF024A41)

On Mon, 2026-05-11 at 17:58 +0900, Masashi Honma wrote:
> > This isn't really right since u32_field_get() exists only within
> > mesh_hwmp.c ... it's probably better to modernise all this while at it:
> 
> Ah, yes. Both the build and tests passed, so I overlooked it.

Yes, it would, but it's basically not self-contained. More of a code
hygiene issue I guess than a real problem right now.

> > and restructure the code accordingly?
> > Anyway, I dunno. Maybe we should just go with your original patch for
> > now. Maybe I'm also asking more of you than others because you have an
> > LLM to help ;-)
> 
> If it is not urgent, I would like to proceed with the requested restructuring.

Oh sure, as far as I'm concerned there's no urgency, I just didn't want
to keep asking you to make changes too much.

> Actually, I only used the LLM to find potential vulnerabilities, and I wrote
> the code myself :)

Oh OK :) Maybe we need that as a kind of Reported-by? Hmm.

Or you could send a separate bug report email, say there Claude found
it, and then do a Closes: link :-p

johannes

      reply	other threads:[~2026-05-11  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8f0a2488540f4a65ea4d837a06225a27a10cc305.camel@sipsolutions.net>
2026-05-08 22:59 ` [PATCH 1/3] Fix overread in PREQ frame processing Masashi Honma
2026-05-08 22:59   ` [PATCH 2/3] Fix overread in PREP " Masashi Honma
2026-05-08 22:59   ` [PATCH 3/3] Fix PERR " Masashi Honma
2026-05-09  9:17   ` [PATCH 1/3] Fix overread in PREQ " Johannes Berg
2026-05-09 23:41     ` Masashi Honma
2026-05-09 23:41       ` [PATCH 2/3] Fix overread in PREP " Masashi Honma
2026-05-09 23:41       ` [PATCH 3/3] Fix PERR " Masashi Honma
2026-05-11  7:47       ` [PATCH 1/3] Fix overread in PREQ " Johannes Berg
2026-05-11  8:58         ` Masashi Honma
2026-05-11  9:01           ` 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=725b56f42b5fec58196e4055bccb74236145986b.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=masashi.honma@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