linux-kernel - Re: [BUILD-FAILURE] next-20091013 - s390x build breaks at mm/fault with !CONFIG_S390_EXEC

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: <20091013105720.GB7542@linux.vnet.ibm.com>
Date:	Tue, 13 Oct 2009 16:27:20 +0530
From:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
To:	Martin Schwidefsky <schwidefsky@...ibm.com>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	heiko.carstens@...ibm.com, linux-s390@...r.kernel.org
Subject: Re: [BUILD-FAILURE] next-20091013 - s390x build breaks at mm/fault
	with !CONFIG_S390_EXEC_PROTECT

* Martin Schwidefsky <schwidefsky@...ibm.com> [2009-10-13 12:33:35]:

> On Tue, 13 Oct 2009 15:36:48 +0530
> Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com> wrote:
> 
> > 	next-20091013 randconfig build breaks on s390, with
> > CONFIG_S390_EXEC_PROTECT=y
> > 
> > arch/s390/mm/fault.c: In function 'signal_return':
> > arch/s390/mm/fault.c:221: error: implicit declaration of function 'is_compat_task'
> > make[1]: *** [arch/s390/mm/fault.o] Error 1
> > 
> > is_compat_task is defined at asm/compat.h, including the 
> > header, helps
> 
> I'll merge that info "[PATCH] fault handler performance optimization" if you
> don't mind.

Please feel free to merge it.

> 
> -- 
> blue skies,
>    Martin.
> 
> "Reality continues to ruin my life." - Calvin.
> 
			
			Kamalesh
--
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/