From: Johannes Berg <johannes@sipsolutions.net>
To: Masashi Honma <masashi.honma@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] Fix overread in PREQ frame processing
Date: Mon, 11 May 2026 09:47:04 +0200 [thread overview]
Message-ID: <ecb7aef2f18cc7c04817be155017a54a45fa579e.camel@sipsolutions.net> (raw)
In-Reply-To: <20260509234143.101237-1-masashi.honma@gmail.com>
Hi,
Please send new versions with a version tag ('v2' in the subject etc.),
and not in the old thread, that just messes up the threads. Ideally tag
which tree these should go to, though I think given the many other
things I'll put this into wireless-next anyway, unless you strongly feel
it needs to be in wireless?
Also, please use appropriate "wifi: mac80211: " prefix in the subject.
> +#define PREQ_IE_PREQ_ID(x) u32_field_get(x, 3, 0)
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:
#define IEEE80211_MESH_HWMP_FLAGS_AE 0x40
struct ieee80211_mesh_hwmp_target {
u8 flags;
u8 addr[ETH_ALEN];
__le32 sn;
} __packed;
struct ieee80211_mesh_hwmp_element {
u8 flags;
u8 hopcount;
u8 ttl;
__le32 preq_id;
u8 orig_addr[ETH_ALEN];
__le32 orig_sn;
/* optional AE, lifetime, metric, target */
u8 variable[];
} __packed;
and then some inlines like
static inline const struct ieee80211_mesh_hwmp_target *
ieee80211_mesh_hwmp_get_target(const struct ieee80211_mesh_hwmp_element *elem)
{
int offs = 8; // seems wrong
if (elem->flags & IEEE80211_MESH_HWMP_FLAGS_AE)
offs += ETH_ALEN;
return (const void *)&elem->variable[offs];
}
static inline u32
ieee80211_mesh_hwmp_get_lifetime(const struct ieee80211_mesh_hwmp_element *elem)
{
int offs = FIXME; // not sure
if (elem->flags & IEEE80211_MESH_HWMP_FLAGS_AE)
offs += ETH_ALEN;
return (const void *)&elem->variable[offs];
}
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 ;-)
johannes
next prev parent reply other threads:[~2026-05-11 7:47 UTC|newest]
Thread overview: 11+ 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 ` Johannes Berg [this message]
2026-05-11 8:58 ` [PATCH 1/3] Fix overread in PREQ " Masashi Honma
2026-05-11 9:01 ` Johannes Berg
2026-05-11 22:25 ` Masashi Honma
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=ecb7aef2f18cc7c04817be155017a54a45fa579e.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.