From: kernel test robot <lkp@intel.com>
To: steven@liquorix.net
Cc: oe-kbuild-all@lists.linux.dev
Subject: [zen:6.5/bbr3 1/1] net/ipv4/tcp_bbr.c:500: undefined reference to `__udivdi3'
Date: Tue, 29 Aug 2023 17:16:49 +0800 [thread overview]
Message-ID: <202308291728.mXShicTc-lkp@intel.com> (raw)
tree: https://github.com/zen-kernel/zen-kernel 6.5/bbr3
head: bcb27e4adacda606c76349bfba3305db6ea83887
commit: bcb27e4adacda606c76349bfba3305db6ea83887 [1/1] bbr3-6.5: initial import
config: i386-randconfig-011-20230829 (https://download.01.org/0day-ci/archive/20230829/202308291728.mXShicTc-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230829/202308291728.mXShicTc-lkp@intel.com/reproduce)
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 <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308291728.mXShicTc-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:500: undefined reference to `__udivdi3'
vim +500 net/ipv4/tcp_bbr.c
474
475 /* Return the number of segments BBR would like in a TSO/GSO skb, given a
476 * particular max gso size as a constraint. TODO: make this simpler and more
477 * consistent by switching bbr to just call tcp_tso_autosize().
478 */
479 static u32 bbr_tso_segs_generic(struct sock *sk, unsigned int mss_now,
480 u32 gso_max_size)
481 {
482 struct bbr *bbr = inet_csk_ca(sk);
483 u32 segs, r;
484 u64 bytes;
485
486 /* Budget a TSO/GSO burst size allowance based on bw (pacing_rate). */
487 bytes = sk->sk_pacing_rate >> sk->sk_pacing_shift;
488
489 /* Budget a TSO/GSO burst size allowance based on min_rtt. For every
490 * K = 2^tso_rtt_shift microseconds of min_rtt, halve the burst.
491 * The min_rtt-based burst allowance is: 64 KBytes / 2^(min_rtt/K)
492 */
493 if (bbr_param(sk, tso_rtt_shift)) {
494 r = bbr->min_rtt_us >> bbr_param(sk, tso_rtt_shift);
495 if (r < BITS_PER_TYPE(u32)) /* prevent undefined behavior */
496 bytes += GSO_LEGACY_MAX_SIZE >> r;
497 }
498
499 bytes = min_t(u32, bytes, gso_max_size - 1 - MAX_TCP_HEADER);
> 500 segs = max_t(u32, bytes / mss_now,
501 sock_net(sk)->ipv4.sysctl_tcp_min_tso_segs);
502 return segs;
503 }
504
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-29 9: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=202308291728.mXShicTc-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=steven@liquorix.net \
/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.