From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
"Hannes Reinecke" <hare@suse.de>,
"Alasdair Kergon" <agk@redhat.com>,
"Mike Snitzer" <snitzer@redhat.com>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] next-20200514 - build issue in drivers/md/dm-zoned-target.c
Date: Sat, 16 May 2020 12:07:03 -0700 [thread overview]
Message-ID: <1589656023.8524.1.camel@HansenPartnership.com> (raw)
In-Reply-To: <367320.1589627953@turing-police>
[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]
On Sat, 2020-05-16 at 07:19 -0400, Valdis Klētnieks wrote:
> Am seeing a build error in next-0514. -0420 built OK.
> building a 'make allmodconfig' on a RPi4 in 32-bit mode.
>
> MODPOST 7575 modules
> ERROR: modpost: "__aeabi_uldivmod" [drivers/md/dm-zoned.ko]
> undefined!
>
> objdump and 'make drivers/md/dm-zoned-target.s' tells
> me that the problem is in function dmz_fixup_devices(), near here:
>
> @ drivers/md/dm-zoned-target.c:806: reg_dev->nr_zones =
> DIV_ROUND_UP(reg_dev->capacity,
> ldr r0, [r6, #56] @ reg_dev_166->capacity, reg_dev_166-
> >capacity
> adds r1, r3, r1 @ tmp316, _227, reg_dev_166->capacity
> adc r0, r2, r0 @ tmp315, _227, reg_dev_166->capacity
> subs r1, r1, #1 @, tmp316,
> @ drivers/md/dm-zoned-target.c:805: reg_dev-
> >zone_nr_sectors = zoned_dev->zone_nr_sectors;
> strd r2, [r6, #80] @, reg_dev,
> @ drivers/md/dm-zoned-target.c:806: reg_dev->nr_zones =
> DIV_ROUND_UP(reg_dev->capacity,
> sbc r0, r0, #0 @, tmp315,
> bl __aeabi_uldivmod @
> @ drivers/md/dm-zoned-target.c:806: reg_dev->nr_zones =
> DIV_ROUND_UP(reg_dev->capacity,
> str r1, [r6, #64] @ tmp306, reg_dev_166->nr_zones
>
> git blame points at this commit:
>
> commit 70978208ec91d798066f4c291bc98ff914bea222
> Author: Hannes Reinecke <hare@suse.de>
> Date: Mon May 11 10:24:30 2020 +0200
>
> dm zoned: metadata version 2
>
> Reverting that commit lets the build complete.
That's because the DIV_ROUND_UP in the patch should actually be
DIV_ROUND_UP_SECTOR_T I think.
James
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-05-16 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 11:19 Valdis Klētnieks
2020-05-16 19:07 ` James Bottomley [this message]
2020-05-18 6:25 ` Hannes Reinecke
2020-05-18 16:44 ` Mike Snitzer
2020-05-18 20:22 ` Valdis Klētnieks
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=1589656023.8524.1.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=valdis.kletnieks@vt.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome