From: kernel test robot <oliver.sang@intel.com>
To: Xu Du <xudu@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Jakub Kicinski <kuba@kernel.org>,
<netdev@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [selftest] 400e658aa0: kernel-selftests-bpf.net.tun.fail
Date: Wed, 18 Mar 2026 15:28:16 +0800 [thread overview]
Message-ID: <202603181411.24db1a78-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests-bpf.net.tun.fail" on:
commit: 400e658aa096cda99b37ce806ed63cfe894c9566 ("selftest: tun: Add test for sending gso packet into tun")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 80234b5ab240f52fa45d201e899e207b9265ef91]
[test failed on linux-next/master f90aadf1c67c8b4969d1e5e6d4fd7227adb6e4d7]
in testcase: kernel-selftests-bpf
version:
with following parameters:
group: net
config: x86_64-rhel-9.4-bpf
compiler: gcc-14
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz (Skylake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202603181411.24db1a78-lkp@intel.com
# timeout set to 3600
# selftests: net: tun
# TAP version 13
# 1..9
# # Starting 9 tests from 5 test cases.
# # RUN tun.delete_detach_close ...
# # OK tun.delete_detach_close
# ok 1 tun.delete_detach_close
# # RUN tun.detach_delete_close ...
# # OK tun.detach_delete_close
# ok 2 tun.detach_delete_close
# # RUN tun.detach_close_delete ...
# # OK tun.detach_close_delete
# ok 3 tun.detach_close_delete
# # RUN tun.reattach_delete_close ...
# # OK tun.reattach_delete_close
# ok 4 tun.reattach_delete_close
# # RUN tun.reattach_close_delete ...
# # OK tun.reattach_close_delete
# ok 5 tun.reattach_close_delete
# # RUN tun_vnet_udptnl.4in4_1mss.send_gso_packet ...
# # OK tun_vnet_udptnl.4in4_1mss.send_gso_packet
# ok 6 tun_vnet_udptnl.4in4_1mss.send_gso_packet
# # RUN tun_vnet_udptnl.6in4_1mss.send_gso_packet ...
# # tun.c:679:send_gso_packet:Expected ret (0) == variant->data_size (1402)
# # send_gso_packet: Test terminated by assertion
# # FAIL tun_vnet_udptnl.6in4_1mss.send_gso_packet
# not ok 7 tun_vnet_udptnl.6in4_1mss.send_gso_packet
# # RUN tun_vnet_udptnl.4in6_1mss.send_gso_packet ...
# # tun.c:679:send_gso_packet:Expected ret (0) == variant->data_size (1402)
# # send_gso_packet: Test terminated by assertion
# # FAIL tun_vnet_udptnl.4in6_1mss.send_gso_packet
# not ok 8 tun_vnet_udptnl.4in6_1mss.send_gso_packet
# # RUN tun_vnet_udptnl.6in6_1mss.send_gso_packet ...
# # tun.c:679:send_gso_packet:Expected ret (0) == variant->data_size (1382)
# # send_gso_packet: Test terminated by assertion
# # FAIL tun_vnet_udptnl.6in6_1mss.send_gso_packet
# not ok 9 tun_vnet_udptnl.6in6_1mss.send_gso_packet
# # FAILED: 6 / 9 tests passed.
# # Totals: pass:6 fail:3 xfail:0 xpass:0 skip:0 error:0
not ok 19 selftests: net: tun # exit=1
/bin/sh: 50: cannot create : Directory nonexistent
# timeout set to 3600
# selftests: net: altnames.sh
# TEST: altnames test [ OK ]
ok 20 selftests: net: altnames.sh
# timeout set to 3600
# selftests: net: amt.sh
# exec of "smcrouted" failed: No such file or directory
ok 21 selftests: net: amt.sh # SKIP
# timeout set to 3600
below [1] is from parent commit as a comparison.
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260318/202603181411.24db1a78-lkp@intel.com
[1] from parent commit:
# timeout set to 3600
# selftests: net: tun
# TAP version 13
# 1..9
# # Starting 9 tests from 5 test cases.
# # RUN tun.delete_detach_close ...
# # OK tun.delete_detach_close
# ok 1 tun.delete_detach_close
# # RUN tun.detach_delete_close ...
# # OK tun.detach_delete_close
# ok 2 tun.detach_delete_close
# # RUN tun.detach_close_delete ...
# # OK tun.detach_close_delete
# ok 3 tun.detach_close_delete
# # RUN tun.reattach_delete_close ...
# # OK tun.reattach_delete_close
# ok 4 tun.reattach_delete_close
# # RUN tun.reattach_close_delete ...
# # OK tun.reattach_close_delete
# ok 5 tun.reattach_close_delete
# # RUN tun_vnet_udptnl.4in4udptnl.basic ...
# # OK tun_vnet_udptnl.4in4udptnl.basic
# ok 6 tun_vnet_udptnl.4in4udptnl.basic
# # RUN tun_vnet_udptnl.6in4udptnl.basic ...
# # OK tun_vnet_udptnl.6in4udptnl.basic
# ok 7 tun_vnet_udptnl.6in4udptnl.basic
# # RUN tun_vnet_udptnl.4in6udptnl.basic ...
# # OK tun_vnet_udptnl.4in6udptnl.basic
# ok 8 tun_vnet_udptnl.4in6udptnl.basic
# # RUN tun_vnet_udptnl.6in6udptnl.basic ...
# # OK tun_vnet_udptnl.6in6udptnl.basic
# ok 9 tun_vnet_udptnl.6in6udptnl.basic
# # PASSED: 9 / 9 tests passed.
# # Totals: pass:9 fail:0 xfail:0 xpass:0 skip:0 error:0
ok 19 selftests: net: tun
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-03-18 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 7:28 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-15 13:36 [linus:master] [selftest] 400e658aa0: kernel-selftests-bpf.net.tun.fail kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202603181411.24db1a78-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=xudu@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.