From: kernel test robot <oliver.sang@intel.com>
To: Kunwu Chan <chentao@kylinos.cn>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<netdev@vger.kernel.org>, <aubrey.li@linux.intel.com>,
<yu.c.chen@intel.com>, <jhs@mojatatu.com>,
<xiyou.wangcong@gmail.com>, <jiri@resnulli.us>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <kunwu.chan@hotmail.com>,
<linux-kernel@vger.kernel.org>, Kunwu Chan <chentao@kylinos.cn>,
<oliver.sang@intel.com>
Subject: Re: [PATCH] net: sched: Fix an endian bug in tcf_proto_create
Date: Mon, 27 Nov 2023 21:59:12 +0800 [thread overview]
Message-ID: <202311271643.12f713c2-oliver.sang@intel.com> (raw)
In-Reply-To: <20231117093110.1842011-1-chentao@kylinos.cn>
Hello,
kernel test robot noticed "kernel-selftests.net.fib_tests.sh.IPv4_rp_filter_tests.rp_filter_passes_loopback_packets.fail" on:
commit: e706cea62528a99bf2a6ea5e420b9726540dde39 ("[PATCH] net: sched: Fix an endian bug in tcf_proto_create")
url: https://github.com/intel-lab-lkp/linux/commits/Kunwu-Chan/net-sched-Fix-an-endian-bug-in-tcf_proto_create/20231117-173323
base: https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git 18de1e517ed37ebaf33e771e46faf052e966e163
patch link: https://lore.kernel.org/all/20231117093110.1842011-1-chentao@kylinos.cn/
patch subject: [PATCH] net: sched: Fix an endian bug in tcf_proto_create
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: net
compiler: gcc-12
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (Cascade Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
besides, we also noticed below tests failed upon this patch.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/group:
lkp-csl-d01/kernel-selftests/debian-12-x86_64-20220629.cgz/x86_64-rhel-8.3-bpf/gcc-12/net
commit:
18de1e517ed37 ("gve: add gve_features_check()")
e706cea62528a ("net: sched: Fix an endian bug in tcf_proto_create")
18de1e517ed37eba e706cea62528a99bf2a6ea5e420
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:10 100% 10:10 kernel-selftests.net.bareudp.sh.IPv4_packets_over_UDPv4.fail
:10 100% 10:10 kernel-selftests.net.bareudp.sh.IPv4_packets_over_UDPv4_multiproto_mode.fail
:10 100% 10:10 kernel-selftests.net.bareudp.sh.IPv4_packets_over_UDPv6.fail
:10 100% 10:10 kernel-selftests.net.bareudp.sh.IPv4_packets_over_UDPv6_multiproto_mode.fail
:10 100% 10:10 kernel-selftests.net.bareudp.sh.IPv6_packets_over_UDPv4.fail
:10 100% 10:10 kernel-selftests.net.bareudp.sh.IPv6_packets_over_UDPv4_multiproto_mode.fail
:10 100% 10:10 kernel-selftests.net.bareudp.sh.IPv6_packets_over_UDPv6.fail
:10 100% 10:10 kernel-selftests.net.bareudp.sh.IPv6_packets_over_UDPv6_multiproto_mode.fail
:10 100% 10:10 kernel-selftests.net.bareudp.sh.Unicast_MPLS_packets_over_UDPv4.fail
:10 100% 10:10 kernel-selftests.net.bareudp.sh.Unicast_MPLS_packets_over_UDPv6.fail
:10 100% 10:10 kernel-selftests.net.bareudp.sh.fail
:10 100% 10:10 kernel-selftests.net.drop_monitor_tests.sh..Capturing_active_software_drops.fail
:10 100% 10:10 kernel-selftests.net.drop_monitor_tests.sh.fail
:10 100% 10:10 kernel-selftests.net.fib_tests.sh.IPv4_rp_filter_tests.rp_filter_passes_local_packets.fail
:10 100% 10:10 kernel-selftests.net.fib_tests.sh.IPv4_rp_filter_tests.rp_filter_passes_loopback_packets.fail
:10 100% 10:10 kernel-selftests.net.rtnetlink.sh.tc_htb_hierarchy.fail
:10 100% 10:10 kernel-selftests.net.test_ingress_egress_chaining.sh.fail
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/202311271643.12f713c2-oliver.sang@intel.com
# timeout set to 1500
# selftests: net: bareudp.sh
# TEST: IPv4 packets over UDPv4 [FAIL]
# TEST: IPv4 packets over UDPv6 [FAIL]
# TEST: IPv6 packets over UDPv4 [FAIL]
# TEST: IPv6 packets over UDPv6 [FAIL]
# TEST: IPv4 packets over UDPv4 (multiproto mode) [FAIL]
# TEST: IPv6 packets over UDPv4 (multiproto mode) [FAIL]
# TEST: IPv4 packets over UDPv6 (multiproto mode) [FAIL]
# TEST: IPv6 packets over UDPv6 (multiproto mode) [FAIL]
# TEST: Unicast MPLS packets over UDPv4 [FAIL]
# TEST: Unicast MPLS packets over UDPv6 [FAIL]
# Some tests failed.
not ok 49 selftests: net: bareudp.sh # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231127/202311271643.12f713c2-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-11-27 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 9:31 [PATCH] net: sched: Fix an endian bug in tcf_proto_create Kunwu Chan
2023-11-17 12:06 ` Pedro Tammela
2023-11-20 10:04 ` Simon Horman
2023-11-20 11:15 ` Kunwu Chan
2023-11-20 15:33 ` Pedro Tammela
2023-11-27 13:59 ` kernel test robot [this message]
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=202311271643.12f713c2-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=chentao@kylinos.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=kunwu.chan@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yu.c.chen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).