On Wed, 2015-02-25 at 02:41 +0530, Krishna Chaitanya wrote: > On Wed, Feb 25, 2015 at 2:17 AM, Johannes Berg > <johan...@sipsolutions.net> wrote: > > On Wed, 2015-02-25 at 02:03 +0530, Krishna Chaitanya wrote: > > > >> Use case2: When changing from HT40-VHT80, the connection goes through > >> but it still connected as HT40 (vht_ie from cfg80211 is returned > >> null). > >> > >> Can you think of any reason why the bss_list is not updated cfg80211? > >> Note: iwconfig and wpa_supplicant both show same behavior. > > > > Well, there's no flushing, only overwriting by new results - but if you > > previuosly got both beacons and probe responses each one will stick > > around until you get them again. > We do have the scan results expiry time of 30secs, that will flush the > results from bss_list right? Even the get_bss checks for aging?
Yes but if you scan in the meantime the scan result is marked as recent again, even if some old data might be kept. Perhaps we should split that into timestamps for probe and beacons separately, but that'd certainly complicate the code significantly for little gain. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
