On Wed, Aug 31, 2005 at 09:22:29PM +0300, Kalle Valo wrote: > Jouni Malinen <[EMAIL PROTECTED]> writes: > > local->hw_priv was initialized only after the interrupt handler was > > registered. This could trigger a NULL pointer dereference in > > prism2_pccard_card_present() that assumed that local->hw_priv is always > > set (and it should have been). Fix this by setting local->hw_priv before > > registering the interrupt handler. > > I was trying to test Jouni's patch but now I can't reproduce the oops > with latest ieee80211-wifi branch and my NULL pointer check removed. > Earlier I could reproduce it every time. Strange.
Triggering this race conditions requires that you are sharing the same interrupt line with another device which is generating interrupts at the same time as Host AP driver is initializing the card. I don't know whether interrupt assignment could have changed in the latest version, but I would guess more like cause would be a difference in, e.g., how other devices are being used at the time Host AP driver was being initialized. -- Jouni Malinen PGP id EFC895FA - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
