From: Fabio Estevam <festevam@gmail.com>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
David Sterba <dsterba@suse.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org
Subject: Re: Linux next-20170407 failed to build on ARM due to usage of mod in btrfs code
Date: Sat, 8 Apr 2017 14:45:34 -0300 [thread overview]
Message-ID: <CAOMZO5B9J15qvrsjOb-e5gk47gA=+2p2yLNLhswG+H3S0L7LXg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.20.1704090002520.35546@x220i>
On Sat, Apr 8, 2017 at 1:02 PM, Icenowy Zheng <icenowy@aosc.io> wrote:
> Hello everyone,
> Today I tried to build a kernel with btrfs enabled on ARM, then when linking
> I met such an error:
>
> ```
> fs/built-in.o: In function `scrub_bio_end_io_worker':
> acl.c:(.text+0x2f0450): undefined reference to `__aeabi_uldivmod'
> fs/built-in.o: In function `scrub_extent_for_parity':
> acl.c:(.text+0x2f0bcc): undefined reference to `__aeabi_uldivmod'
> fs/built-in.o: In function `scrub_raid56_parity':
> acl.c:(.text+0x2f12a8): undefined reference to `__aeabi_uldivmod'
> acl.c:(.text+0x2f15c4): undefined reference to `__aeabi_uldivmod'
> ```
>
> These functions are found at fs/btrfs/scrub.c .
>
> After disabling btrfs the kernel is successfully built.
I see the same error with ARM imx_v6_v7_defconfig + btrfs support.
Looks like it is caused by commit 7d0ef8b4dbbd220 ("Btrfs: update
scrub_parity to use u64 stripe_len").
WARNING: multiple messages have this Message-ID (diff)
From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: Linux next-20170407 failed to build on ARM due to usage of mod in btrfs code
Date: Sat, 8 Apr 2017 14:45:34 -0300 [thread overview]
Message-ID: <CAOMZO5B9J15qvrsjOb-e5gk47gA=+2p2yLNLhswG+H3S0L7LXg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.20.1704090002520.35546@x220i>
On Sat, Apr 8, 2017 at 1:02 PM, Icenowy Zheng <icenowy@aosc.io> wrote:
> Hello everyone,
> Today I tried to build a kernel with btrfs enabled on ARM, then when linking
> I met such an error:
>
> ```
> fs/built-in.o: In function `scrub_bio_end_io_worker':
> acl.c:(.text+0x2f0450): undefined reference to `__aeabi_uldivmod'
> fs/built-in.o: In function `scrub_extent_for_parity':
> acl.c:(.text+0x2f0bcc): undefined reference to `__aeabi_uldivmod'
> fs/built-in.o: In function `scrub_raid56_parity':
> acl.c:(.text+0x2f12a8): undefined reference to `__aeabi_uldivmod'
> acl.c:(.text+0x2f15c4): undefined reference to `__aeabi_uldivmod'
> ```
>
> These functions are found at fs/btrfs/scrub.c .
>
> After disabling btrfs the kernel is successfully built.
I see the same error with ARM imx_v6_v7_defconfig + btrfs support.
Looks like it is caused by commit 7d0ef8b4dbbd220 ("Btrfs: update
scrub_parity to use u64 stripe_len").
next prev parent reply other threads:[~2017-04-08 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 16:02 Linux next-20170407 failed to build on ARM due to usage of mod in btrfs code Icenowy Zheng
2017-04-08 16:02 ` Icenowy Zheng
2017-04-08 17:45 ` Fabio Estevam [this message]
2017-04-08 17:45 ` Fabio Estevam
2017-04-08 17:45 ` Fabio Estevam
2017-04-08 18:38 ` Adam Borowski
2017-04-08 18:38 ` Adam Borowski
2017-04-08 18:38 ` Adam Borowski
2017-04-08 21:07 ` [PATCH] btrfs: scrub: use do_div() for 64-by-32 division Adam Borowski
2017-04-08 21:07 ` Adam Borowski
2017-04-09 3:58 ` Adam Borowski
2017-04-09 3:58 ` Adam Borowski
2017-04-10 1:13 ` Adam Borowski
2017-04-10 1:13 ` Adam Borowski
2017-04-10 11:13 ` David Sterba
2017-04-10 11:13 ` David Sterba
2017-04-10 12:50 ` Austin S. Hemmelgarn
2017-04-10 12:50 ` Austin S. Hemmelgarn
2017-04-10 18:41 ` Liu Bo
2017-04-10 18:41 ` Liu Bo
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='CAOMZO5B9J15qvrsjOb-e5gk47gA=+2p2yLNLhswG+H3S0L7LXg@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=icenowy@aosc.io \
--cc=jbacik@fb.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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.