On 08/19/2015 11:56 PM, Rafał Miłecki wrote:
On 16 August 2015 at 08:55, Arend van Spriel <arend@xxxxxxxxxxxx> wrote:
From: Hante Meuleman <meuleman@xxxxxxxxxxxx>
Next generation devices will have firmware which will have more
than 256 flowrings. This patch increases the maximum number of
supported flowrings to 512.
Reviewed-by: Arend Van Spriel <arend@xxxxxxxxxxxx>
Reviewed-by: Franky (Zhenhui) Lin <frankyl@xxxxxxxxxxxx>
Reviewed-by: Pieter-Paul Giesberts <pieterpg@xxxxxxxxxxxx>
Signed-off-by: Hante Meuleman <meuleman@xxxxxxxxxxxx>
Signed-off-by: Arend van Spriel <arend@xxxxxxxxxxxx>
This is a patch that for my device triggers:
Unable to handle kernel NULL pointer dereference at virtual address 00000014
It seems to happen even when using only 1 AP interface.
Hi Rafał,
What happens is that your platform has no memory to allocate a flowring
for tx and there is a bug in handling the returned error. Can you try it
with following applied. You will still have memory issue so for OpenWrt
you may need to limit to 256 anyway. Hante found another issue with
hash_id in struct brcmf_flowring so we are not entirely sure which issue
caused the null pointer deref so your feedback is appreciated.
Regards,
Arend
---
drivers/net/wireless/brcm80211/brcmfmac/flowring.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/brcm80211/brcmfmac/flowring.c
b/drivers/net/wi
index 5b7a8ee..9fb50b3 100644
--- a/drivers/net/wireless/brcm80211/brcmfmac/flowring.c
+++ b/drivers/net/wireless/brcm80211/brcmfmac/flowring.c
@@ -151,11 +151,11 @@ u32 brcmf_flowring_create(struct brcmf_flowring
*flow, u8
break;
}
if (i == flow->nrofrings)
- return -ENOMEM;
+ return BRCMF_FLOWRING_INVALID_ID;
ring = kzalloc(sizeof(*ring), GFP_ATOMIC);
if (!ring)
- return -ENOMEM;
+ return BRCMF_FLOWRING_INVALID_ID;
memcpy(hash[hash_idx].mac, mac, ETH_ALEN);
hash[hash_idx].fifo = fifo;
--
1.9.1
--
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
