linux-kernel - RE: [ 26/89] mwifiex: update config

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <477F20668A386D41ADCC57781B1F70430D1432F5B5@SC-VEXCH1.marvell.com>
Date:	Mon, 4 Feb 2013 11:37:46 -0800
From:	Bing Zhao <bzhao@...vell.com>
To:	Ben Hutchings <ben@...adent.org.uk>,
	Amitkumar Karwar <akarwar@...vell.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	"John W. Linville" <linville@...driver.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: RE: [ 26/89] mwifiex: update config_bands during infra association

Hi Ben,

> > From: Amitkumar Karwar <akarwar@...vell.com>
> >
> > commit d7b9c5204e9c6810a20d509ee47bc70419096e59 upstream.
> >
> > Currently "adapter->config_bands" is updated during infra
> > association only if channel is provided by user in "iw connect"
> > command. config_bands is used while preparing association
> > request to calculate supported rates by intersecting our rates
> > with the rates advertised by AP.
> >
> > There is corner case in which we include zero rates in
> > supported rates TLV based on previous IBSS network history,
> > which leads to association failure.
> >
> > This patch fixes the problem by correctly updating config_bands.
> >
> > Signed-off-by: Amitkumar Karwar <akarwar@...vell.com>
> > Signed-off-by: Bing Zhao <bzhao@...vell.com>
> > Signed-off-by: John W. Linville <linville@...driver.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> [...]
> 
> Is this fix needed for earlier kernel versions (3.0, 3.2, 3.4)?  If so,
> could you provide backports?

This patch is not needed for earlier kernel 3.0, 3.2, and 3.4.

Thanks,
Bing