Re: [PATCH next V2] brcmfmac: avoid writing channel out of allocated array

2017-01-04 Thread Rafał Miłecki
On 4 January 2017 at 11:48, Arend Van Spriel wrote: > On 4-1-2017 11:40, Rafał Miłecki wrote: >> On 4 January 2017 at 10:39, Arend Van Spriel >> wrote: >>> On 3-1-2017 17:49, Rafał Miłecki wrote: From: Rafał Miłecki Our code was assigning number of channels to the index variable b

Re: [PATCH next V2] brcmfmac: avoid writing channel out of allocated array

2017-01-04 Thread Arend Van Spriel
On 4-1-2017 11:40, Rafał Miłecki wrote: > On 4 January 2017 at 10:39, Arend Van Spriel > wrote: >> On 3-1-2017 17:49, Rafał Miłecki wrote: >>> From: Rafał Miłecki >>> >>> Our code was assigning number of channels to the index variable by >>> default. If firmware reported channel we didn't predict

Re: [PATCH next V2] brcmfmac: avoid writing channel out of allocated array

2017-01-04 Thread Rafał Miłecki
On 4 January 2017 at 10:39, Arend Van Spriel wrote: > On 3-1-2017 17:49, Rafał Miłecki wrote: >> From: Rafał Miłecki >> >> Our code was assigning number of channels to the index variable by >> default. If firmware reported channel we didn't predict this would >> result in using that initial index

Re: [PATCH next V2] brcmfmac: avoid writing channel out of allocated array

2017-01-04 Thread Arend Van Spriel
On 3-1-2017 17:49, Rafał Miłecki wrote: > From: Rafał Miłecki > > Our code was assigning number of channels to the index variable by > default. If firmware reported channel we didn't predict this would > result in using that initial index value and writing out of array. This > never happened so f

[PATCH next V2] brcmfmac: avoid writing channel out of allocated array

2017-01-03 Thread Rafał Miłecki
From: Rafał Miłecki Our code was assigning number of channels to the index variable by default. If firmware reported channel we didn't predict this would result in using that initial index value and writing out of array. This never happened so far (we got a complete list of supported channels) bu