linux-kernel - Re: 2.6.25-rc8-mm1 (mips build failure)

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]

Date:	Wed, 2 Apr 2008 21:06:23 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Christoph Lameter <clameter@....com>,
	Ralf Baechle <ralf@...ux-mips.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	dmitri.vorobiev@...il.com, linux-kernel@...r.kernel.org
Subject: Re: 2.6.25-rc8-mm1 (mips build failure)

On Wed, Apr 02, 2008 at 11:33:42AM -0700, Christoph Lameter wrote:
> On Wed, 2 Apr 2008, Andrew Morton wrote:
> 
> > i386 generates
> > 
> > ->NR_PAGEFLAGS $18 __NR_PAGEFLAGS       #
> 
> > mips generates
> > 
> > ->NR_PAGEFLAGS 18 __NR_PAGEFLAGS         #
> 
> For some reason the asm-offset.c for mips generates it differently and the 
> sed expression in kbuild is different. So it does not match.

When the asm-offset stuff were consolidated the mips variant
did not match the others.
I do not recall if I ever tried this on a mips tool-chain and as
my dev box is busted atm I cannot even test it out now.

I would be happy if we could kill the MIPS specific sed expression
in the top-level Kbuild file.

Ralf - can you take a look at this and see if mips really generates
different assembler syntax which warrants the different sed expression.

If mips really needs a different sed expression then we should adjust
it so the output is similar to the other archs.

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