On 2 June 2016 at 07:20, Arend Van Spriel <arend.vanspriel@xxxxxxxxxxxx> wrote:
> Op 2 jun. 2016 06:55 schreef "Rafał Miłecki" <zajec5@xxxxxxxxx>:
>>
>> On 1 June 2016 at 23:13, Arend van Spriel <arend@xxxxxxxxxxxx> wrote:
>> > From: Franky Lin <franky.lin@xxxxxxxxxxxx>
>> >
>> > A regression was introduced in commit 9c349892ccc9 ("brcmfmac: revise
>> > handling events in receive path") which moves eth_type_trans() call
>> > to brcmf_rx_frame(). Msgbuf layer doesn't use brcmf_rx_frame() but
>> > invokes
>> > brcmf_netif_rx() directly. In such case the Ethernet header was not
>> > stripped out resulting in null pointer dereference in the networking
>> > stack.
>> >
>> > (...)
>> >
>> > Reported-by: Grey Christoforo <grey@xxxxxxxxxxxxxxx>
>>
>> Well, I reported this as well, over a month ago :(
>
> Hi Rafał,
>
> Dived into my emails and shameful to admit you are right. Totally missed it.
> Sorry for unintended disregard.
It happens, thanks for the fix! :)
--
Rafał
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
