On Mon, 2009-07-27 at 12:12 -0400, Pavel Roskin wrote: > On Mon, 2009-07-27 at 18:02 +0200, Johannes Berg wrote: > > > Actually, you're using ath5k, right? So we can see what > > info->control.vif points to after ath5k has used the skb, because > > apparently it's a valid pointer at least, just not a real vif pointer > > any more. > > I'm using ath9k. > > Here's something interesting I have found. sdata->dev is valid if > info->flags is 0x14091 and not valid if it's 0x12091. > > 0x4000 is IEEE80211_TX_INTFL_NEED_TXPROCESSING and 0x2000 is > IEEE80211_TX_INTFL_RCALGO. > > This patch prevents any panics. Moreover, I get a connection with the > correct PSK. Ok. So the question is where that skb is coming from that's causing the issues (your patch leaks it btw) johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
