Jakub Kicinski <kuba@xxxxxxxxxx> wrote: > On Tue, 18 Jul 2023 09:52:29 +0200 Florian Westphal wrote: > > __NLA_IS_BEINT_TYPE(tp) isn't useful. NLA_BE16/32 are identical to > > NLA_U16/32, the only difference is that it tells the netlink validation > > functions that byteorder conversion might be needed before comparing > > the value to the policy min/max ones. > > > > After this change all policy macros that can be used with UINT types, > > such as NLA_POLICY_MASK() can also be used with NLA_BE16/32. > > > > This will be used to validate nf_tables flag attributes which > > are in bigendian byte order. > > Semi-related, how well do we do with NLA_F_NET_BYTEORDER? Looks incomplete at best. > On a quick grep we were using it in the kernel -> user > direction but not validating on input. Is that right? Looks like ipset is the only user, it sets it for kernel->user dir. I see ipset userspace even sets it on user -> kernel dir but like you say, its not checked and BE encoding is assumed on kernel side. >From a quick glance in ipset all Uxx types are always treated as bigendian, which would mean things should not fall apart if ipset stops announcing NLA_F_NET_BYTEORDER. Not sure its worth risking any breakage though. I suspect that in practice, given both producer and consumer need to agree of the meaning of type "12345" anyway its easier to just agree on the byte ordering as well. Was there a specific reason for the question?
