Hi Ben, On Fri, Apr 01, 2016 at 02:12:10PM -0700, [email protected] wrote: > From: Ben Greear <[email protected]> > > Not sure this can happen, but seems like a reasonable sanity > check.
[shafi] possibly if the peer is removed and the bit is not cleared in the driver ? when the new peer occupies the slot > > Signed-off-by: Ben Greear <[email protected]> > --- > drivers/net/wireless/ath/ath10k/txrx.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/net/wireless/ath/ath10k/txrx.c > b/drivers/net/wireless/ath/ath10k/txrx.c > index a779a4e..2edef8a 100644 > --- a/drivers/net/wireless/ath/ath10k/txrx.c > +++ b/drivers/net/wireless/ath/ath10k/txrx.c > @@ -309,6 +309,7 @@ void ath10k_peer_map_event(struct ath10k_htt *htt, > ath10k_warn(ar, /*ATH10K_DBG_HTT,*/ "htt peer map vdev %d peer %pM id > %d\n", > ev->vdev_id, ev->addr, ev->peer_id); > > + WARN_ON(ar->peer_map[ev->peer_id] && (ar->peer_map[ev->peer_id] != > peer)); > ar->peer_map[ev->peer_id] = peer; > set_bit(ev->peer_id, peer->peer_ids); > exit: > -- > 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
