This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1919147 Title: ip_defrag.sh in net from ubuntu_kernel_selftests failed with exit code 255 on F-oem-5.6 Status in ubuntu-kernel-tests: In Progress Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] The ip_defrag.sh test in net from kernel-selftest failed with exit code 255: # selftests: net: ip_defrag.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 [Fix] * aba69d49fb49c9 ("selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support") This patch can be cherry-picked into OEM-5.6 [Test Case] Run this script after building the net test in kselftest directory (linux/tools/testing/selftests) from the kernel tree: make TARGETS=net cd net sudo ./ip_defrag.sh With this patch applied the test will pass without any issue. [Where problems could occur] Change limited to the test case only. And this has already included in other kernels, it's unlikely to cause problems. [Original Bug Report] Issue found on 5.6.0-1050.54 - oem The ip_defrag.sh test failed with: # selftests: net: ip_defrag.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 I don't think this can be called as a regression, since the ubuntu_kernel_selftests test was removed and added back to the test suite until the most recent cycle. And this issue can be reproduced with 5.6.0-1048-oem as well. Note that we have another issue for this test filed against F-oem-5.6 in before, see bug 1908498 It looks like there are several changes after this test since then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1919147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
