All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Baokun Li <libaokun1@huawei.com>
Cc: Jens Axboe <axboe@kernel.dk>, Josef Bacik <josef@toxicpanda.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure while building Linus' tree
Date: Thu, 9 Sep 2021 18:25:25 +1000	[thread overview]
Message-ID: <20210909182525.372ee687@canb.auug.org.au> (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
include/linux/overflow.h).

-- 
Cheers,
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: 11+ 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-09 22:50   ` Nick Desaulniers
2021-09-10 22:02   ` Nick Desaulniers
2021-09-10 22:02     ` Nick Desaulniers
2021-09-10 22:17     ` Nick Desaulniers
2021-09-10 22:17       ` Nick Desaulniers
2021-09-10 22:26       ` Nick Desaulniers
2021-09-10 22:26         ` Nick Desaulniers
2021-09-10 22:34         ` 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:
  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=20210909182525.372ee687@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=axboe@kernel.dk \
    --cc=josef@toxicpanda.com \
    --cc=libaokun1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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.