On Fri, 2019-06-28 at 16:40 +0200, Jason A. Donenfeld wrote: > People are inclined to stuff random things into cb->args[n] because it > looks like an array of integers. Sometimes people even put u64s in there > with comments noting that a certain member takes up two slots. The > horror! Really this should mirror the usage of skb->cb, which are just > 48 opaque bytes suitable for casting a struct. Then people can create > their usual casting macros for accessing strongly typed members of a > struct. > > As a plus, this also gives us the same amount of space on 32bit and 64bit. > > Signed-off-by: Jason A. Donenfeld <[email protected]> > Cc: Johannes Berg <[email protected]>
Reviewed-by: Johannes Berg <[email protected]> I think this makes a lot of sense - we've got a mess here in many places, e.g. look at struct nl80211_dump_wiphy_state in nl82011.c, I think that could fit into the ctx[] since those don't all need to be 'long' (int or even shorter would be OK), we just want many more fields and somehow it didn't occur to me to cast that "long args[]" array to another struct ... Thanks for doing this! johannes
