From: kernel test robot <oliver.sang@intel.com>
To: <shiming.cheng@mediatek.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Lena Wang <lena.wang@mediatek.com>, <netdev@vger.kernel.org>,
<willemdebruijn.kernel@gmail.com>, <edumazet@google.com>,
<davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>,
<matthias.bgg@gmail.com>, <linux-kernel@vger.kernel.org>,
<shiming.cheng@mediatek.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH net] net: drop pulled SKB_GSO_FRAGLIST skb
Date: Mon, 20 May 2024 13:05:23 +0800 [thread overview]
Message-ID: <202405201037.5e36a83-oliver.sang@intel.com> (raw)
In-Reply-To: <20240428143010.18719-1-shiming.cheng@mediatek.com>
Hello,
kernel test robot noticed "kernel-selftests.net.udpgro_fwd.sh.fail" on:
commit: 7ed67c5ee988b506bd05e115e9e8299bccbabffd ("[PATCH net] net: drop pulled SKB_GSO_FRAGLIST skb")
url: https://github.com/intel-lab-lkp/linux/commits/shiming-cheng-mediatek-com/net-drop-pulled-SKB_GSO_FRAGLIST-skb/20240430-133823
base: https://git.kernel.org/cgit/linux/kernel/git/davem/net.git ba1cb99b559e3b12db8b65ca9ff03358ea318064
patch link: https://lore.kernel.org/all/20240428143010.18719-1-shiming.cheng@mediatek.com/
patch subject: [PATCH net] net: drop pulled SKB_GSO_FRAGLIST skb
in testcase: kernel-selftests
version: kernel-selftests-x86_64-977d51cf-1_20240508
with following parameters:
group: net
compiler: gcc-13
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)
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/202405201037.5e36a83-oliver.sang@intel.com
# timeout set to 3600
# selftests: net: udpgro_fwd.sh
# IPv4
# No GRO ok
# GRO frag list ./udpgso_bench_rx: wrong packet number! got 0, expected 10
#
# fail client exit code 0, server 1
# GRO fwd ok
# UDP fwd perf udp tx: 1488 MB/s 25250 calls/s 25250 msg/s
# udp rx: 1 MB/s 1280 calls/s
# udp tx: 1501 MB/s 25471 calls/s 25471 msg/s
# udp rx: 1 MB/s 1280 calls/s
# udp tx: 1512 MB/s 25656 calls/s 25656 msg/s
# udp rx: 1 MB/s 1380 calls/s
# UDP GRO fwd perf udp rx: 337 MB/s 272896 calls/s
# udp tx: 2183 MB/s 37033 calls/s 37033 msg/s
# udp rx: 376 MB/s 304320 calls/s
# udp tx: 2162 MB/s 36675 calls/s 36675 msg/s
# udp rx: 402 MB/s 325376 calls/s
# udp tx: 2167 MB/s 36758 calls/s 36758 msg/s
# GRO frag list over UDP tunnel ok
# GRO fwd over UDP tunnel ok
# IPv6
# No GRO ok
# GRO frag list ./udpgso_bench_rx: wrong packet number! got 0, expected 10
#
# fail client exit code 0, server 1
# GRO fwd ok
# UDP fwd perf udp rx: 37 MB/s 30033 calls/s
# udp tx: 2220 MB/s 37661 calls/s 37661 msg/s
# udp rx: 99 MB/s 80141 calls/s
# udp tx: 2179 MB/s 36973 calls/s 36973 msg/s
# udp tx: 2161 MB/s 36654 calls/s 36654 msg/s
# udp rx: 104 MB/s 84775 calls/s
# UDP GRO fwd perf udp rx: 162 MB/s 131584 calls/s
# udp tx: 2113 MB/s 35848 calls/s 35848 msg/s
# udp rx: 263 MB/s 213370 calls/s
# udp tx: 2097 MB/s 35574 calls/s 35574 msg/s
# udp rx: 217 MB/s 175616 calls/s
# udp tx: 2107 MB/s 35748 calls/s 35748 msg/s
# GRO frag list over UDP tunnel ok
# GRO fwd over UDP tunnel ok
not ok 53 selftests: net: udpgro_fwd.sh # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240520/202405201037.5e36a83-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-05-20 5:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 14:30 [PATCH net] net: drop pulled SKB_GSO_FRAGLIST skb shiming.cheng
2024-04-29 13:25 ` Willem de Bruijn
2024-05-15 9:05 ` Lena Wang (王娜)
2024-05-20 5:05 ` 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=202405201037.5e36a83-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lena.wang@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=shiming.cheng@mediatek.com \
--cc=willemdebruijn.kernel@gmail.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).