From: 'Marcelo Ricardo Leitner' > Sent: 13 September 2019 14:20 ... > Interestingly, we have/had the opposite problem with netlink. Like, it > was allowing too much flexibility, such as silently ignoring unknown > fields (which is what would happen with a new app running on an older > kernel would trigger here) is bad because the app cannot know if it > was actually used or not. Some gymnastics in the app could cut through > the fat here, like probing getsockopt() return size, but then it may > as well probe for the right sockopt to be used. Yes, it would also work if the kernel checked that all 'unexpected' fields were zero (up to some sanity limit of a few kB). Then an application complied with a 'new' header would work with an old kernel provided it didn't try so set any new fields. (And it zeroed the entire structure.) But you have to start off with that in mind. Alternatively stop the insanity of setting multiple options with one setsockopt call. If multiple system calls are an issue implement a system call that will set multiple options on the same socket. (Maybe through a CMSG()-like buffer). Then the application can set the ones it wants without having to do the read-modify-write sequence needed for some of the SCTP ones. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
