From: Kalle Valo <kvalo@kernel.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
David Lin <yu-hao.lin@nxp.com>,
Francesco Dolcini <francesco@dolcini.it>
Subject: Re: [PATCH] [RFC] mwifiex: Fix NULL pointer deref
Date: Mon, 24 Jun 2024 14:07:53 +0300 [thread overview]
Message-ID: <87zfraha46.fsf@kernel.org> (raw)
In-Reply-To: <ZnYDwjS293Cb8O1f@google.com> (Brian Norris's message of "Fri, 21 Jun 2024 15:50:42 -0700")
Brian Norris <briannorris@chromium.org> writes:
> On Fri, Jun 21, 2024 at 11:07:27AM +0200, Sascha Hauer wrote:
>> I am running plain wpa_supplicant -i mlan0 with this config:
>>
>> network={
>> ssid="somessid"
>> mode=2
>> frequency=2412
>> key_mgmt=WPA-PSK WPA-PSK-SHA256
>> proto=RSN
>> group=CCMP
>> pairwise=CCMP
>> psk="12345678"
>> }
>>
>> wait for the AP to be established, <ctrl-c> wpa_supplicant and start it
>> again.
>
> Thanks. I still can't reproduce, but that's OK. From your fuller
> description now, it seems it depends on the particulars of the bss
> indices in use, and maybe my device/firmware is behaving differently.
> Anyway, your current description and patch below make a lot more sense.
Indeed, this makes a lot more sense. Thank you both for getting to the
bottom of it!
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-06-24 11:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 7:08 [PATCH] [RFC] mwifiex: Fix NULL pointer deref Sascha Hauer
2024-06-19 8:05 ` Kalle Valo
2024-06-20 19:48 ` Brian Norris
2024-06-21 9:07 ` Sascha Hauer
2024-06-21 22:50 ` Brian Norris
2024-06-24 11:07 ` Kalle Valo [this message]
2024-06-24 16:20 ` Francesco Dolcini
2024-07-02 13:32 ` Sascha Hauer
2024-07-02 20:36 ` Francesco Dolcini
2024-07-03 7:24 ` Sascha Hauer
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=87zfraha46.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=briannorris@chromium.org \
--cc=francesco@dolcini.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=yu-hao.lin@nxp.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.