On Thu, Feb 05, 2009 at 12:55:07PM +0100, Johannes Berg wrote: > Seems ok to me, since wext limits us to this anyway... But can we rely > on userspace to (a) use the exactly largest buffer size and (b) be able > to interpret that? (a) Currently not, but once people realize that the length field has a maximum value of 65535, using it as the largest attempt sounds like the most logical choice. In other words, yes, this will require a small change in programs that care (wpa_supplicant, which I already changed; iwlist; etc.), but the change is minimal and not doing this does not break anything new. (b) Yes, user space apps better be prepared to read the results even if the last entry is truncated (can happen with current kernel). There is no clear way for the app to know that there could be more scan results (well, it could guess that this is the case if the returned buffer is very close to 64 kB), but it is not like scanning is that reliable operation anyway, so applications better be prepared to not always find every BSS in the results. -- Jouni Malinen PGP id EFC895FA -- 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
