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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0704261320090.5678@schroedinger.engr.sgi.com>
Date:	Thu, 26 Apr 2007 13:23:19 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Andy Whitcroft <apw@...dowen.org>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.21-rc7-mm2 -- PPC link failure

On Thu, 26 Apr 2007, Andy Whitcroft wrote:

> > Gcc 3.3 works just fine on other platforms like i386. This is more likely 
> > a platform issue. If we disable it then only for <= gcc 3.3 on ppc. If 
> > problems crop up with other platforms then we can expand on it.
> 
> I was thinking that it would be nasty to have a set of platform
> specific, compiler specific ifdefs in here.  I was more thinking of just
> making this a BUG for all platforms.  This does result in slightly later
> detection but this is a constant mode only, so any bad use of kmalloc()
> would be picked up on first boot in testing always.
> 
> I think that would be sufficient and safe even against the worst
> optimiser (none).  Plus much less horrible to look at?

The build time detection is quite important for NUMA since structures keep 
growing. I'd like to keep that. In fact I would really like a build time 
detection. If a too large kmalloc occurs then the compile should stop at 
that point and the kernel should not link at all.

See my patch @ http://marc.info/?l=linux-kernel&m=117752927203466&w=2

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ