> > > >On Fri, Apr 01, 2016 at 02:12:08PM -0700, [email protected] wrote: > >>From: Ben Greear <[email protected]> > >> > >>Otherwise, the txrx-compl-task may access some bad memory? > > > >good to mention when this happens, will be helpful ifsome one recreates > >the issue and matches your call trace > > The backtraces were all over the place because the driver was writing to > memory after it was freed, so I am not sure they are worth while. I'm sure I > posted > some to the mailing lists around the time where I was working on this, but > since > I was fighting several different problems, hard to know exactly what was what.
[shafi] sure Ben, lets wait for the comments from ath10k reviewers. > > Thanks, > Ben > > >>Signed-off-by: Ben Greear <[email protected]> > >>--- > >> 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 > >>b/drivers/net/wireless/ath/ath10k/htt_tx.c > >>index 07b960e..58e88d3 100644 > >>--- a/drivers/net/wireless/ath/ath10k/htt_tx.c > >>+++ b/drivers/net/wireless/ath/ath10k/htt_tx.c > >>@@ -376,6 +376,8 @@ void ath10k_htt_tx_free(struct ath10k_htt *htt) > >> { > >> int size; > >> > >>+ tasklet_kill(&htt->txrx_compl_task); > >>+ > >> idr_for_each(&htt->pending_tx, ath10k_htt_tx_clean_up_pending, htt->ar); > >> idr_destroy(&htt->pending_tx); > >> > >>-- > >>2.4.3 > > > >regards, > >shafi > > > >> > >> > >>_______________________________________________ > >>ath10k mailing list > >>[email protected] > >>http://lists.infradead.org/mailman/listinfo/ath10k > > > >_______________________________________________ > >ath10k mailing list > >[email protected] > >http://lists.infradead.org/mailman/listinfo/ath10k > > > > -- > Ben Greear <[email protected]> > Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
