linux-kernel - Re: linux-next: tip tree 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] [day] [month] [year] [list]

Message-ID: <84144f021001042339r29f151feja00d7af12a82c9a2@mail.gmail.com>
Date:	Tue, 5 Jan 2010 09:39:40 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Thiago Farina <tfransosi@...il.com>
Subject: Re: linux-next: tip tree build failure

On Mon, Jan 4, 2010 at 6:32 PM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
>> Hi all,
>>
>> Today's linux-next build (s390x defconfig) failed like this:
>>
>> kernel/panic.c:134: error: 'CALLER_ADDR0' undeclared (first use in this function)
>>
>> Caused by commit eba3fe4416f3cc2ce043fb304b6c35a69dca3bdb ("kernel: Use
>> CALLER_ADDR0 macro").
>
> Thanks - apparently CALLER_ADDR0 isnt generally available. I've reverted this
> patch for now.

Btw, we have _RET_IP_ which is pretty much the same thing and it is
available everywhere (SLUB uses it).
--
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/