linux-kernel - Re: x86 arch updates also broke s390

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: <20080131102454.GB27157@elte.hu>
Date:	Thu, 31 Jan 2008 11:24:54 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Martin Schwidefsky <schwidefsky@...ibm.com>
Cc:	Adrian Bunk <bunk@...sta.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, Nick Piggin <npiggin@...e.de>,
	heiko.carstens@...ibm.com, linux390@...ibm.com
Subject: Re: x86 arch updates also broke s390


* Martin Schwidefsky <schwidefsky@...ibm.com> wrote:

> On Thu, 2008-01-31 at 02:33 +0200, Adrian Bunk wrote:
> > <--  snip  -->
> > 
> > ...
> >   CC      arch/s390/kernel/asm-offsets.s
> > In file included from 
> > /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/s390/kernel/asm-offsets.c:7:
> > /home/bunk/linux/kernel-2.6/git/linux-2.6/include/linux/sched.h: In
> > function 'spin_needbreak':
> > /home/bunk/linux/kernel-2.6/git/linux-2.6/include/linux/sched.h:1931:
> > error: implicit declaration of function '__raw_spin_is_contended'
> > make[2]: *** [arch/s390/kernel/asm-offsets.s] Error 1
> > 
> > <--  snip  -->
> 
> Defining GENERIC_LOCKBREAK in arch/s390/Kconfig takes care of it. I'll 
> cook up a patch and queue it in git390.

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/