On 9/17/19 1:12 AM, Marcelo Henrique Cerri wrote:
So the problem arises because the headers we have in userspace might be older and not match what we have in the kernel. In that case, the actual value of AF_MAX in the userspace headers might be a valid protocol family in the new kernel. That happens relatively often for us because we support different kernel versions at the same time in a given Ubuntu series.
Right. This is an evolving use-case for kselftest to make it easier to run on distribution kernels.
An alternative is to use the headers we have in the kernel tree, but I believe that might cause other issues.
Kselftest is tied to the kernel in such as way that you do need to use the kernel headers to compile. Do you run newer tests on older kernels? Where do you build them? What I would like to see is fixing the test to run on older kernels and not changing the tests to suit older kernel needs. This definitely isn't a change that is good to make. We have to come with a better way to solve this. Could you please send me the errors you are seeing so I can help you find a better solution. thanks, -- Shuah
