From: Yufen Yu <yuyufen@huawei.com>
To: Song Liu <song@kernel.org>, kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-raid <linux-raid@vger.kernel.org>,
Song Liu <songliubraving@fb.com>
Subject: Re: [song-md:md-next 9/14] ERROR: modpost: "__udivdi3" undefined!
Date: Thu, 23 Jul 2020 11:33:31 +0800 [thread overview]
Message-ID: <056d7a5f-bc67-194e-4908-8677d82a4ac0@huawei.com> (raw)
In-Reply-To: <CAPhsuW66LPe0feQtgns=Tp2JYvUNT6vDnqg6j1inq+WT8uQrsQ@mail.gmail.com>
On 2020/7/23 5:31, Song Liu wrote:
> On Wed, Jul 22, 2020 at 2:21 PM kernel test robot <lkp@intel.com> wrote:
>>
>> tree: git://git.kernel.org/pub/scm/linux/kernel/git/song/md.git md-next
>> head: fe630de009d0729584d79c78f43121e07c745fdc
>> commit: e236858243d7a8e0ac60972d2f9522146088a736 [9/14] md/raid5: set default stripe_size as 4096
>> config: m68k-sun3_defconfig (attached as .config)
>> compiler: m68k-linux-gcc (GCC) 9.3.0
>> reproduce (this is a W=1 build):
>> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> git checkout e236858243d7a8e0ac60972d2f9522146088a736
>> # save the attached .config to linux build tree
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>, old ones prefixed by <<):
>>
>>>> ERROR: modpost: "__udivdi3" [drivers/md/raid456.ko] undefined!
>
> Yufen, could you please look into this one? I guess it is caused by ilog2().
>
This compiler error is caused by 64bit division on on 32-bit architectures.
I have send the fix patch.
Thanks,
Yufen
prev parent reply other threads:[~2020-07-23 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 21:20 [song-md:md-next 9/14] ERROR: modpost: "__udivdi3" undefined! kernel test robot
2020-07-22 21:31 ` Song Liu
2020-07-23 3:33 ` Yufen Yu [this message]
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=056d7a5f-bc67-194e-4908-8677d82a4ac0@huawei.com \
--to=yuyufen@huawei.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-raid@vger.kernel.org \
--cc=lkp@intel.com \
--cc=song@kernel.org \
--cc=songliubraving@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).