linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ganapathi Bhat <ganapathi.bhat@nxp.com>
To: "Pali Rohár" <pali@kernel.org>,
	"Amitkumar Karwar" <amitkarwar@gmail.com>,
	"Xinming Hu" <huxinming820@gmail.com>,
	"Kalle Valo" <kvalo@codeaurora.org>,
	"David S. Miller" <davem@davemloft.net>,
	"Cathy Luo" <cluo@marvell.com>,
	"Avinash Patil" <patila@marvell.com>,
	"Marek Behún" <marek.behun@nic.cz>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [EXT] [PATCH] mwifiex: Fix memory corruption in dump_station
Date: Sat, 16 May 2020 08:07:16 +0000	[thread overview]
Message-ID: <VI1PR04MB43668507151CCB7810F5EEEF8FBA0@VI1PR04MB4366.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200515075924.13841-1-pali@kernel.org>

Hi Pali,

> The mwifiex_cfg80211_dump_station() uses static variable for iterating over
> a linked list of all associated stations (when the driver is in UAP role). This has
> a race condition if .dump_station is called in parallel for multiple interfaces.
> This corruption can be triggered by registering multiple SSIDs and calling, in
> parallel for multiple interfaces
>     iw dev <iface> station dump

Thanks for this change.
 
Acked-by: Ganapathi Bhat <ganapathi.bhat@nxp.com>

Regards,
Ganapathi

  reply	other threads:[~2020-05-16  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  7:59 [PATCH] mwifiex: Fix memory corruption in dump_station Pali Rohár
2020-05-16  8:07 ` Ganapathi Bhat [this message]
2020-05-18 12:19 ` Kalle Valo

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=VI1PR04MB43668507151CCB7810F5EEEF8FBA0@VI1PR04MB4366.eurprd04.prod.outlook.com \
    --to=ganapathi.bhat@nxp.com \
    --cc=amitkarwar@gmail.com \
    --cc=cluo@marvell.com \
    --cc=davem@davemloft.net \
    --cc=huxinming820@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marek.behun@nic.cz \
    --cc=netdev@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=patila@marvell.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;
as well as URLs for NNTP newsgroup(s).