applied
-
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
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->
Jouni Malinen <[EMAIL PROTECTED]> writes:
>> applied, but let us know when the root cause is found...
>
> 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_pr
On Sun, Aug 28, 2005 at 07:26:12PM -0400, Jeff Garzik wrote:
> applied, but let us know when the root cause is found...
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 lo
applied, but let us know when the root cause is found...
-
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
With my Buffalo WLI-CF-S11G PC Card kernel oopses every time in
prism2_interrupt() when I try load the hostap module. local->hw_priv is null
during the first call to prism2_interrupt(). It feels like
interrupts are enabled too early, or something.
This patch fixes the symptom, but not the cause.
