From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [zen:5.15/bbr2 14/28] net/ipv4/tcp_bbr.c:313: undefined reference to `__udivdi3'
Date: Fri, 05 Nov 2021 00:17:56 +0800 [thread overview]
Message-ID: <202111050048.w91ynJS1-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]
tree: https://github.com/zen-kernel/zen-kernel 5.15/bbr2
head: de136008f854ed5dd68ee7b7f65ba23c2df6b960
commit: 16b8d7dfec9d9f7b8d182e58148af031bd2c4afa [14/28] net-tcp: re-generalize TSO sizing in TCP CC module API
config: i386-randconfig-a003-20211104 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/zen-kernel/zen-kernel/commit/16b8d7dfec9d9f7b8d182e58148af031bd2c4afa
git remote add zen https://github.com/zen-kernel/zen-kernel
git fetch --no-tags zen 5.15/bbr2
git checkout 16b8d7dfec9d9f7b8d182e58148af031bd2c4afa
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: net/ipv4/tcp_bbr.o: in function `bbr_tso_segs_generic':
>> net/ipv4/tcp_bbr.c:313: undefined reference to `__udivdi3'
vim +313 net/ipv4/tcp_bbr.c
299
300 /* Return the number of segments BBR would like in a TSO/GSO skb, given
301 * a particular max gso size as a constraint.
302 */
303 static u32 bbr_tso_segs_generic(struct sock *sk, unsigned int mss_now,
304 u32 gso_max_size)
305 {
306 u32 segs;
307 u64 bytes;
308
309 /* Budget a TSO/GSO burst size allowance based on bw (pacing_rate). */
310 bytes = sk->sk_pacing_rate >> sk->sk_pacing_shift;
311
312 bytes = min_t(u32, bytes, gso_max_size - 1 - MAX_TCP_HEADER);
> 313 segs = max_t(u32, bytes / mss_now, bbr_min_tso_segs(sk));
314 return segs;
315 }
316
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 28840 bytes --]
reply other threads:[~2021-11-04 16:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202111050048.w91ynJS1-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.