Search Linux Wireless

Re: mac80211 locking: tasklet vs. non-tasklet

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Feb 25, 2008 at 1:00 PM, Johannes Berg
<johannes@xxxxxxxxxxxxxxxx> wrote:
> > > >  > A disconnection can happen due to
>  > > >  > device resume or internal recoverable error. In this cases I would
>  > > >  > expect mac to try associate again upon such trigger.
>  > > >
>  > > >  I guess that's just missing. You can stop the queues but you can't tell
>  > > >  mac80211 that you reset the hw.
>  > >
>  > > If there is no objection we will introduce some notification
>  > > mechanism...suggestions are welcome as well.
>  >
>  > I have no objection, though I'm unsure what precisely you want. What,
>  > for example, if you're running hostapd and your hardware resets? Can you
>  > keep station tables etc.?
>
>  I mean, if the hw simply resets quickly then I would expect the
>  association to withstand that, no?

I would notify mac only if driver cannot deal with reset and also
mac80211 configuration have to be reapplied such as start association
process again in STA mode.   It would be probably security problem if
we put just station into associated mode without proper association
process.
If in AP mode  stations have only soft state that it would be probably
not necessary to reset station table.

Tomas

>  johannes
>
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux