From: Torsten Schmitz <noreply.torsten at gmail.com>
To: iwd at lists.01.org
Subject: Re: [PATCH] station: Prevent a NULL pointer access
Date: Sun, 07 Nov 2021 02:02:58 +0100 [thread overview]
Message-ID: <CFJ558V5FNXE.2CP12NH8WWZ8X@hostname> (raw)
In-Reply-To: 3c0e6c34-3054-276c-9f0f-44c57b173f84@gmail.com
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
> Could you provide a bit more info about the
> network setup you managed to trigger this on?
We have a mishmash of older and newer APs,
some supporting mesh some don't all advertising the same SSID.
There is an open and closed network.
owe_info->ssid in the crash was the SSID of the open network.
I do not use the open network and connecting to it with iwd
fails.
> This would imply that this network has a set of APs that advertise the
> same SSID, but do not advertise an OWE transition element,
> and some APs that do advertise it?
Sounds plausible.
>I.e. some legacy APs that do not have a hidden partner?
iwd shows three hidden APs for that open network. Their addresses
suggest they belong to the older APs without mesh support.
So I think it is the older APs that do have hidden partners
and advertise OWE transitions.
> > + if (!owe_info)
> > + return false;
> > +
> This should not be necessary since owe_info is checked right before
> invoking
> this function.
Oh, that's right.
These big if statements seem good at hiding stuff.
Perhaps "O2: Try to avoid complex if body" should apply
to the if conditions as well?
next reply other threads:[~2021-11-07 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 1:02 Torsten Schmitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-06 17:56 [PATCH] station: Prevent a NULL pointer access Denis Kenzior
2021-11-06 15:53 noreply.torsten
2021-11-06 2:36 Torsten Schmitz
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=CFJ558V5FNXE.2CP12NH8WWZ8X@hostname \
--to=iwd@lists.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