From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Qu Wenruo <wqu@suse.com>, David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>
Subject: next-20210511 - btrfs build failure on arm
Date: Tue, 11 May 2021 14:08:02 -0400 [thread overview]
Message-ID: <564681.1620756482@turing-police> (raw)
An arm allmodconfig build died with:
ERROR: modpost: "__aeabi_uldivmod" [fs/btrfs/btrfs.ko] undefined!
Some digging around with nm and looking at the assembler points at:
@ /usr/src/linux-next/fs/btrfs/extent_io.c:2676: const int nr_bits = (end + 1 - start) / fs_info->sectorsize_bits;
adds r1, r1, #1 @, tmp552,
adc r0, r0, #0 @, tmp551,
ldr r3, [r5, #1576] @ tmp2, _47->sectorsize_bits
bl __aeabi_uldivmod @
Introduced by this commit:
commit 6512659d8f13015dccfb38a13c6d117d22572019
Author: Qu Wenruo <wqu@suse.com>
Date: Mon May 3 10:08:55 2021 +0800
btrfs: submit read time repair only for each corrupted sector
Looks like that line could use something from include/linux/math.h
next reply other threads:[~2021-05-11 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 18:08 Valdis Klētnieks [this message]
2021-05-11 18:09 ` next-20210511 - btrfs build failure on arm David Sterba
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=564681.1620756482@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wqu@suse.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 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.