From: Ben Greear
If WMI and/or firmware has issues removing the peer object,
then we still need to clean up the peer object in the driver.
Signed-off-by: Ben Greear
---
drivers/net/wireless/ath/ath10k/mac.c | 12 ++--
1 file changed,
From: Ben Greear
Not sure this can happen, but seems like a reasonable sanity
check.
Signed-off-by: Ben Greear
---
drivers/net/wireless/ath/ath10k/txrx.c | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Ben Greear
While debugging OS crashes due to firmware crashes, I enabled
kasan, and it noticed that peer objects were being used-after-freed.
Looks like there are two places we could be leaving stale references
in the peer-map, so clean that up.
Signed-off-by:
From: Ben Greear
We must not attempt to send WMI packets while holding the data-lock,
as it may deadlock:
BUG: sleeping function called from invalid context at
drivers/net/wireless/ath/ath10k/wmi.c:1824
in_atomic(): 1, irqs_disabled(): 0, pid: 2878, name:
From: Ben Greear
Otherwise, the txrx-compl-task may access some bad memory?
Signed-off-by: Ben Greear
---
drivers/net/wireless/ath/ath10k/htt_tx.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/wireless/ath/ath10k/htt_tx.c
On 03/31/2016 11:12 PM, Michal Kazior wrote:
On 31 March 2016 at 22:59, wrote:
From: Ben Greear
Otherwise, the txrx-compl-task may access some bad memory?
Signed-off-by: Ben Greear
---
On 03/31/2016 11:09 PM, Michal Kazior wrote:
On 31 March 2016 at 22:59, wrote:
From: Ben Greear
Not sure this can happen, but seems like a reasonable sanity
check.
Signed-off-by: Ben Greear
---
Re-posting text only as it was blocked by most mailing list servers:
The original attachment can be fetched at:
http://kazikcz.github.io/dl/2016-04-01-flent-ath10k-dql.tar.gz
On 25 March 2016 at 10:55, Michal Kazior wrote:
> On 25 March 2016 at 10:39, Michal Kazior
On 31 March 2016 at 23:57, Ben Greear wrote:
> On 03/31/2016 02:30 PM, Ben Greear wrote:
>>
>> hacked 4.4.6 (with most of linux.ath ath10k patches backported), hacked
>> 10.4.3 firmware.
>>
>> I enabled kasan to help track down various bugs. This one has me a bit
>>
On 1 April 2016 at 07:23, Ben Greear wrote:
>
>
> On 03/31/2016 10:18 PM, Michal Kazior wrote:
>>
>> On 31 March 2016 at 18:44, Ben Greear wrote:
>>>
>>> On 03/30/2016 11:51 PM, Michal Kazior wrote:
>
>
>>>
>>> So, I am using MSI-X, I guess?
>>>
On 31 March 2016 at 22:59, wrote:
[...]
> @@ -812,6 +813,15 @@ static void ath10k_peer_cleanup(struct ath10k *ar, u32
> vdev_id)
> ar->peer_map[peer_id] = NULL;
> }
>
> + /* Double check that peer is properly
On 31 March 2016 at 22:59, wrote:
> From: Ben Greear
>
> Otherwise, the txrx-compl-task may access some bad memory?
>
> Signed-off-by: Ben Greear
> ---
> drivers/net/wireless/ath/ath10k/htt_tx.c | 2 ++
> 1 file
On 31 March 2016 at 22:59, wrote:
> From: Ben Greear
>
> Not sure this can happen, but seems like a reasonable sanity
> check.
>
> Signed-off-by: Ben Greear
> ---
> drivers/net/wireless/ath/ath10k/txrx.c | 1 +
> 1
13 matches
Mail list logo