LKML Archive on
help / color / mirror / Atom feed
From: Stephen Rothwell <>
To: Baokun Li <>
Cc: Jens Axboe <>, Josef Bacik <>,
	Linux Kernel Mailing List <>,
	Linux Next Mailing List <>
Subject: linux-next: build failure while building Linus' tree
Date: Thu, 9 Sep 2021 18:25:25 +1000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

Hi all,

Building Linus' tree, today's linux-next build (powerpc
ppc6xx_defconfig gcc4.9) failed like this:

ERROR: modpost: "__divdi3" [drivers/block/nbd.ko] undefined!

Caused by commit

  fad7cd3310db ("nbd: add the check to prevent overflow in __nbd_ioctl()")

The added check_mul_overflow() call is being passed 64 bit values.
COMPILER_HAS_GENERIC_BUILTIN_OVERFLOW is not set for this build (see

Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-09-09  8:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09  8:25 Stephen Rothwell [this message]
2021-09-09 22:50 ` linux-next: build failure while building Linus' tree Nick Desaulniers
2021-09-10 22:02   ` Nick Desaulniers
2021-09-10 22:17     ` Nick Desaulniers
2021-09-10 22:26       ` Nick Desaulniers
2021-09-10 22:34         ` Nick Desaulniers

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).