linux-kernel - Re: 2.6.23-rc8 build failure: __you_cannot_kmalloc_that_much in dmi_id

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: <20071002232642.568ea660@hyperion.delvare>
Date:	Tue, 2 Oct 2007 23:26:42 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.23-rc8 build failure: __you_cannot_kmalloc_that_much in
 dmi_id_init

On Mon, 1 Oct 2007 23:54:12 +0200, Jean Delvare wrote:
> On Mon, 1 Oct 2007 22:54:47 +0200, Jean Delvare wrote:
> > 2.6.23-rc8 and 2.6.23-rc8-git4 fail to build on one of my test
> > machines, with:
> > 
> > drivers/built-in.o(.init.text+0x780e): In function `dmi_id_init':
> > : undefined reference to `__you_cannot_kmalloc_that_much'
> > 
> > The code is allocating sizeof(struct device) so it really shouldn't be
> > a problem. I have no idea what's wrong. That's on i386, very old
> > machine (Pentium 166MMX / Intel TX chipset), with gcc 3.2.3 and
> > binutils 2.14.90.0.6. 2.6.22.9 compiles fine on the same system (but it
> > doesn't include dmi-id so it's not very surprising).
> > 
> > .config attached.
> 
> More information: building the same config on a much more recent system
> works fine. This seems to point at a toolchain issue.

More information:
* No improvement in 2.6.23-rc9.
* Building the same config on a different system with the same
  toolchain, fails the same. So it's not just one system acting weirdly,
  the bug can be reproduced.
* I tried arbitrary values for the kzalloc() in dmi-id.c, the bottom line
  is that anything above 64 bytes triggers the bug.
* The same kzalloc() in a different driver doesn't trigger the bug.

I'm puzzled, no idea what to try next.

-- 
Jean Delvare
-
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/