From: Mike Snitzer <snitzer@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: Scott Bauer <scott.bauer@intel.com>,
kbuild-all@01.org, dm-devel@redhat.com, agk@redhat.com,
linux-kernel@vger.kernel.org, keith.busch@intel.com,
jonathan.derrick@intel.com
Subject: Re: [PATCH v4 1/2] dm-unstripe: unstripe RAID 0/dm-striped device
Date: Wed, 20 Dec 2017 11:09:47 -0500 [thread overview]
Message-ID: <20171220160947.GB18363@redhat.com> (raw)
In-Reply-To: <201712201815.9AIAEPWE%fengguang.wu@intel.com>
On Wed, Dec 20 2017 at 5:21am -0500,
kbuild test robot <lkp@intel.com> wrote:
> Hi Scott,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on dm/for-next]
> [also build test ERROR on v4.15-rc4]
> [cannot apply to next-20171220]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Scott-Bauer/dm-unstripe/20171220-121845
> base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
> config: arm-allyesconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=arm
>
> All errors (new ones prefixed by >>):
>
> drivers/md/dm-unstripe.o: In function `set_ctr':
> >> dm-unstripe.c:(.text+0x438): undefined reference to `__aeabi_uldivmod'
> dm-unstripe.c:(.text+0x450): undefined reference to `__aeabi_uldivmod'
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
These reports are no longer relevant given the code has changed since
v4. In particular these 64-bit divide and mod in v4 no longer exist:
+ u64 tot_sec, mod;
...
+ tot_sec = i_size_read(bbdev->bd_inode) >> SECTOR_SHIFT;
+ mod = tot_sec % target->chunk_sectors;
+
+ if (ti->len == 1)
+ ti->len = (tot_sec / tot_drives) - mod;
next prev parent reply other threads:[~2017-12-20 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 17:28 [PATCH v4 0/2] dm-unstripe Scott Bauer
2017-12-18 17:28 ` [PATCH v4 1/2] dm-unstripe: unstripe RAID 0/dm-striped device Scott Bauer
2017-12-18 19:11 ` Randy Dunlap
2017-12-18 18:52 ` Scott Bauer
2017-12-18 19:32 ` Mike Snitzer
2017-12-18 19:37 ` Mike Snitzer
2017-12-20 10:01 ` kbuild test robot
2017-12-20 10:01 ` kbuild test robot
2017-12-20 10:21 ` kbuild test robot
2017-12-20 10:21 ` kbuild test robot
2017-12-20 16:09 ` Mike Snitzer [this message]
2017-12-18 17:28 ` [PATCH v4 2/2] dm-unstripe: Add documentation for unstripe target Scott Bauer
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=20171220160947.GB18363@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jonathan.derrick@intel.com \
--cc=kbuild-all@01.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=scott.bauer@intel.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.