mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Neil Brown <neilb@suse.de>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: tip: origin tree build failure (x86, 32-bit, allyesconfig)
Date: Thu, 22 Apr 2010 11:12:41 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1004221111220.26046@i5.linux-foundation.org> (raw)
In-Reply-To: <20100422070610.GA18884@elte.hu>



On Thu, 22 Apr 2010, Ingo Molnar wrote:
> 
> All 32-bit x86 builds (x86, allyesconfig) that enable RAID are failing with 
> this build failure:
> 
>  drivers/built-in.o: In function `raid5_compute_sector':
>  raid5.c:(.text+0x2e42ac): undefined reference to `__umoddi3'
>  raid5.c:(.text+0x2e42d8): undefined reference to `__umoddi3'
>  raid5.c:(.text+0x2e42ff): undefined reference to `__umoddi3'
>  raid5.c:(.text+0x2e4327): undefined reference to `__umoddi3'
>  raid5.c:(.text+0x2e4385): undefined reference to `__umoddi3'
>  drivers/built-in.o:raid5.c:(.text+0x2e43bc): more undefined references to `__umoddi3' follow
> 
> Caused by this commit:
> 
>   35f2a59: md/raid5: allow for more than 2^31 chunks.

Gaah, yes.

How about just making it "unsigned long" instead of sector_t, and telling 
people that if they have more than 2**32 chunks in their RAID array, they 
should damn well use a 64-bit CPU.

The alternative, of course, is to use "sector_div()" everywhere. Neil?

		Linus

  reply	other threads:[~2010-04-22 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 22:52 [PULL REQUEST] minor md updates for 2.6.34 Neil Brown
2010-04-22  7:06 ` tip: origin tree build failure (x86, 32-bit, allyesconfig) Ingo Molnar
2010-04-22 18:12   ` Linus Torvalds [this message]
2010-04-22 21:13     ` Neil Brown

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=alpine.LFD.2.00.1004221111220.26046@i5.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=neilb@suse.de \
    /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