On 2016年08月03日 15:52, Johannes Berg wrote:
I'm actually half thinking that we could just remove all restrictions
on this and allow any u16 value of this field, and rely on
wpa_supplicant to do the right thing... Then we don't have to update
this if we ever want to do something new either.
What do you think? What does the validation actually help us with?
I think checking the bits here is better than allowing all values.
Because if we allow any values for ht_opmode, kernel developer needs to
care about any bit combination working well. For example, kernel
developer should test there is not any unexpected thing when non-GF and
non-HT both flags are enabled. If we check invalid bit at the entrance,
we don't need to care anymore about invalid combination. In any case we
need to care about combination. Then, it is more easy to do it near the
entrance.
And I think checking only in wpa_supplicant is not good idea. Because
other user application can access to the kernel API. If invalid flag
combination causes kernel panic, it could be kernel vulnerability.
Masashi Honma.
--
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
