linux-kernel - tip: origin tree build failure (x86, 32-bit, allyesconfig)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100422070610.GA18884@elte.hu>
Date:	Thu, 22 Apr 2010 09:06:10 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Neil Brown <neilb@...e.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: tip: origin tree build failure (x86, 32-bit, allyesconfig)


* Neil Brown <neilb@...e.de> wrote:

> are available in the git repository at:
> 
>   git://neil.brown.name/md/ for-linus

( Note, i'm re-using this old MD pull request thread to report a bug in a pull 
  request you sent to Linus in the past two days. I havent found the pull 
  request nor the patch on lkml. )

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.

I've reverted the commit from -tip for now.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/