[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZruOERPfLACNlw7P@google.com>
Date: Tue, 13 Aug 2024 09:47:13 -0700
From: Brian Norris <briannorris@...omium.org>
To: Sascha Hauer <s.hauer@...gutronix.de>
Cc: Francesco Dolcini <francesco@...cini.it>, Kalle Valo <kvalo@...nel.org>,
Yogesh Ashok Powar <yogeshp@...vell.com>,
Bing Zhao <bzhao@...vell.com>,
"John W. Linville" <linville@...driver.com>,
Amitkumar Karwar <akarwar@...vell.com>,
Avinash Patil <patila@...vell.com>,
Kiran Divekar <dkiran@...vell.com>, linux-wireless@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel@...gutronix.de,
stable@...r.kernel.org
Subject: Re: [PATCH] mwifiex: duplicate static structs used in driver
instances
On Fri, Aug 09, 2024 at 10:11:33AM +0200, Sascha Hauer wrote:
> mwifiex_band_2ghz and mwifiex_band_5ghz are statically allocated, but
> used and modified in driver instances. Duplicate them before using
> them in driver instances so that different driver instances do not
> influence each other.
Ugh, I caught a few problems like this on the first several passes of
review, but I missed a few more. Thanks for the catches.
> This was observed on a board which has one PCIe and one SDIO mwifiex
> adapter. It blew up in mwifiex_setup_ht_caps(). This was called with
> the statically allocated struct which is modified in this function.
>
> Cc: stable@...r.kernel.org
> Fixes: d6bffe8bb520 ("mwifiex: support for creation of AP interface")
> Signed-off-by: Sascha Hauer <s.hauer@...gutronix.de>
Acked-by: Brian Norris <briannorris@...omium.org>
Powered by blists - more mailing lists