2010-01-04 12:59:41

by Stephen Rothwell

[permalink] [raw]
Subject: linux-next: tip tree build failure

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").

--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/

Attachments:
(No filename) (352.00 B)
 (No filename) (198.00 B)
 Download all attachments

2010-01-04 16:32:17

by Ingo Molnar

[permalink] [raw]
Subject: Re: linux-next: tip tree build failure


* Stephen Rothwell <[email protected]> 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.

Ingo

2010-01-05 03:40:07

by Stephen Rothwell

[permalink] [raw]
Subject: Re: linux-next: tip tree build failure

Hi Ingo,

On Mon, 4 Jan 2010 17:32:00 +0100 Ingo Molnar <[email protected]> wrote:
>
>
> Thanks - apparently CALLER_ADDR0 isnt generally available. I've reverted this
> patch for now.

Thanks.

--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/

Attachments:
(No filename) (295.00 B)
 (No filename) (198.00 B)
 Download all attachments

2010-01-05 07:39:44

by Pekka Enberg

[permalink] [raw]
Subject: Re: linux-next: tip tree build failure

On Mon, Jan 4, 2010 at 6:32 PM, Ingo Molnar <[email protected]> wrote:
>
> * Stephen Rothwell <[email protected]> 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).