From: Fathi Boudra <fathi.boudra@xxxxxxxxxx> Date: Sat, 23 Sep 2017 14:27:15 +0300 > On 23 September 2017 at 04:20, David Miller <davem@xxxxxxxxxxxxx> wrote: >> From: Orson Zhai <orson.zhai@xxxxxxxxxx> >> Date: Fri, 22 Sep 2017 18:17:17 +0800 >> >>> The TPACKET_V3 test of PACKET_TX_RING will fail with kernel version >>> lower than v4.11. Supported code of tx ring was add with commit id >>> <7f953ab2ba46: af_packet: TX_RING support for TPACKET_V3> at Jan. 3 >>> of 2017. >>> >>> So skip this item test instead of reporting failing for old kernels. >>> >>> Signed-off-by: Orson Zhai <orson.zhai@xxxxxxxxxx> >> >> The whole point is to make sure the kernel in which the selftest >> code is present functions properly. >> >> There are many tests in selftests that only work on recent kernels. > > For the background, a similar discussion happened on this thread: > https://lkml.org/lkml/2017/6/22/802 > > There's cases where we'd like to run latest selftests on stable kernels. > You're right, there are many tests in selftests that only work on > recent kernels and we intend to fix it. > Skipping gracefully a test because the feature is missing on the > kernel under test is preferred to fail. This approach is extremely ill advised. It is hard enough to get developers to add new tests in the first place. Having the extra burdon of needing to make the test work on older kernels is going to discourage test writing even more. If you want to "backport" tests, handle them the same way -stable backports are done. With extreme care and making sure they get backported to the kernel they actually would work on. -- To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
