From: Robin Hack <rhack@redhat.com>
To: Eunbong Song <eunb.song@samsung.com>
Cc: ak@linux.intel.com, sasha.levin@oracle.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: tools/liblockdep: Build failure
Date: Tue, 1 Apr 2014 10:02:58 +0200 [thread overview]
Message-ID: <20140401080258.GA10429@bigoook.brq.redhat.com> (raw)
In-Reply-To: <22212997.138341396332274687.JavaMail.weblogic@epml01>
Hi.
I have same issue.
I investigated output of gcc -E and I found that asmlinkage macro isn't
expanded as is expected.
$ grep asmlinkage common.o
asmlinkage extern void lockdep_sys_exit(void);
On Tue, Apr 01, 2014 at 06:04:35AM +0000, Eunbong Song wrote:
>
> There is tools/liblockdep build failure.
> I have been trying to find the cause and i found commit id 63f9a7fde715352e0769302527670542a664b981 is the casue.
>
> Author: Andi Kleen <ak@linux.intel.com>
> Date: Sat Feb 8 08:52:01 2014 +0100
>
> asmlinkage: Make lockdep_sys_exit asmlinkage
>
> lockdep_sys_exit can be called from assembler code, so make it
> asmlinkage.
>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@kernel.org>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> Link: http://lkml.kernel.org/r/1391845930-28580-5-git-send-email-ak@linux.intel.com
> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
>
> diff --git a/include/linux/lockdep.h b/include/linux/lockdep.h
> index 92b1bfc..7df9aa6 100644
> --- a/include/linux/lockdep.h
> +++ b/include/linux/lockdep.h
> @@ -265,7 +265,7 @@ extern void lockdep_info(void);
> extern void lockdep_reset(void);
> extern void lockdep_reset_lock(struct lockdep_map *lock);
> extern void lockdep_free_key_range(void *start, unsigned long size);
> -extern void lockdep_sys_exit(void);
> +extern asmlinkage void lockdep_sys_exit(void);
>
> extern void lockdep_off(void);
> extern void lockdep_on(void);
> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> index eb8a547..c8b6753 100644
> --- a/kernel/locking/lockdep.c
> +++ b/kernel/locking/lockdep.c
> @@ -4191,7 +4191,7 @@ void debug_show_held_locks(struct task_struct *task)
> }
> EXPORT_SYMBOL_GPL(debug_show_held_locks);
>
> -void lockdep_sys_exit(void)
> +asmlinkage void lockdep_sys_exit(void)
> {
> struct task_struct *curr = current;
next prev parent reply other threads:[~2014-04-01 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 6:04 tools/liblockdep: Build failure Eunbong Song
2014-04-01 8:02 ` Robin Hack [this message]
2014-04-01 8:11 ` Robin Hack
2014-04-01 10:21 ` [PATCH] " Robin Hack
2014-04-01 10:34 ` Robin Hack
2014-04-01 15:34 ` Andi Kleen
2014-04-01 15:47 ` Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140401080258.GA10429@bigoook.brq.redhat.com \
--to=rhack@redhat.com \
--cc=ak@linux.intel.com \
--cc=eunb.song@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox