On Mon, 2008-03-31 at 16:05 -0400, John W. Linville wrote: > On Sun, Mar 30, 2008 at 10:33:19AM +0200, Johannes Berg wrote: > > > The first one is that there is no actual expiration of BSS structs. Each > > BSS struct has a 'last_update' member that contains (in jiffies) the > > time this item was last updated. This means that we accumulate BSS > > information forever, but due to the 'last_update' only the last few > > items will be returned to the user on asking for a scan result. This > > obviously has problems since a rogue station could bombard us with fake > > probe responses and cause us to build a huge BSS list which is never > > again freed until the hardware is deregistered. This will need to be > > fixed, of course. > > Assuming this was fixed, does the rest of this issue go away? > It seems like it would. Sort of, it'll go away as soon as the info is expired, but you still won't be able to switch over right away. > Should we consider allowing the beacon to update the info if > last_update is old enough to keep the BSS out of the scan results? That, maybe, and maybe also if we don't want to associate with that network right away or something. Really, I think this needs somebody to dig into the specs, figure out which things can change from where, and mostly rewrite it all appropriately. I for sure won't have time to do that. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
