From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: mingo@kernel.org, torvalds@linux-foundation.org,
rusty@rustcorp.com.au, rdunlap@infradead.org, jeremy@goop.org,
arnd@arndb.de, dl9pf@gmx.de, akpm@linux-foundation.org,
sparse@chrisli.org, tglx@linutronix.de, hpa@zytor.com,
linux-kernel@vger.kernel.org, anil.s.keshavamurthy@intel.com,
davem@davemloft.net, ananth@in.ibm.com, chrisw@sous-sol.org,
akataria@vmware.com,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
anton Kolesov <Anton.Kolesov@synopsys.com>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: kprobes broken in linux-next (was Re: [tip:perf/kprobes] kprobes: Introduce NOKPROBE_SYMBOL() macro to maintain kprobes blacklist)
Date: Fri, 02 May 2014 10:13:43 +0900 [thread overview]
Message-ID: <5362F147.6030901@hitachi.com> (raw)
In-Reply-To: <5361DB14.7010406@synopsys.com>
(2014/05/01 14:26), Vineet Gupta wrote:
> On Thursday 24 April 2014 04:28 PM, tip-bot for Masami Hiramatsu wrote:
>> Commit-ID: 376e242429bf8539ef39a080ac113c8799840b13
>> Gitweb: http://git.kernel.org/tip/376e242429bf8539ef39a080ac113c8799840b13
>> Author: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
>> AuthorDate: Thu, 17 Apr 2014 17:17:05 +0900
>> Committer: Ingo Molnar <mingo@kernel.org>
>> CommitDate: Thu, 24 Apr 2014 10:02:56 +0200
>>
>> kprobes: Introduce NOKPROBE_SYMBOL() macro to maintain kprobes blacklist
>>
>> Introduce NOKPROBE_SYMBOL() macro which builds a kprobes
>> blacklist at kernel build time.
>>
> ....
>
>> diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
>> index 146e4ff..40ceb3c 100644
>> --- a/include/asm-generic/vmlinux.lds.h
>> +++ b/include/asm-generic/vmlinux.lds.h
>> @@ -109,6 +109,14 @@
>> #define BRANCH_PROFILE()
>> #endif
>>
>> +#ifdef CONFIG_KPROBES
>> +#define KPROBE_BLACKLIST() VMLINUX_SYMBOL(__start_kprobe_blacklist) = .; \
>> + *(_kprobe_blacklist) \
>> + VMLINUX_SYMBOL(__stop_kprobe_blacklist) = .;
>> +#else
>> +#define KPROBE_BLACKLIST()
>> +#endif
>> +
>> #ifdef CONFIG_EVENT_TRACING
>> #define FTRACE_EVENTS() . = ALIGN(8); \
>> VMLINUX_SYMBOL(__start_ftrace_events) = .; \
>> @@ -507,6 +515,7 @@
>> *(.init.rodata) \
>> FTRACE_EVENTS() \
>> TRACE_SYSCALLS() \
>> + KPROBE_BLACKLIST() \
>> MEM_DISCARD(init.rodata) \
>> CLK_OF_TABLES() \
>> RESERVEDMEM_OF_TABLES() \
>
> Linux-next fails to boot on ARC due to misaligned __start_kprobe_blacklist. Patch
> below fixes it.
>
> ------------------------>
>>From c5afc4ebf9c1c094a260e2aaff6c5b3106063039 Mon Sep 17 00:00:00 2001
> From: Vineet Gupta <vgupta@synopsys.com>
> Date: Thu, 1 May 2014 10:47:29 +0530
> Subject: [PATCH] kprobes: Ensure blacklist data is aligned
>
> ARC Linux (not supporting native unaligned access) was failing to boot
> because __start_kprobe_blacklist was not aligned.
>
> This was because per generated vmlinux.lds it was emitted right next
> to .rodata with strings etc hence could be randomly unaligned.
>
> Fix that by ensuring a word alignment. While 4 would suffice for 32bit
> arches and problem at hand, it is probably better to put 8.
>
> | Path: (null) CPU: 0 PID: 1 Comm: swapper Not tainted
> | 3.15.0-rc3-next-20140430 #2
> | task: 8f044000 ti: 8f01e000 task.ti: 8f01e000
> |
> | [ECR ]: 0x00230400 => Misaligned r/w from 0x800fb0d3
> | [EFA ]: 0x800fb0d3
> | [BLINK ]: do_one_initcall+0x86/0x1bc
> | [ERET ]: init_kprobes+0x52/0x120
>
> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Thanks!
> ---
> include/asm-generic/vmlinux.lds.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
> index 40ceb3ceba79..8e0204a68c74 100644
> --- a/include/asm-generic/vmlinux.lds.h
> +++ b/include/asm-generic/vmlinux.lds.h
> @@ -110,7 +110,8 @@
> #endif
>
> #ifdef CONFIG_KPROBES
> -#define KPROBE_BLACKLIST() VMLINUX_SYMBOL(__start_kprobe_blacklist) = .; \
> +#define KPROBE_BLACKLIST() . = ALIGN(8); \
> + VMLINUX_SYMBOL(__start_kprobe_blacklist) = .; \
> *(_kprobe_blacklist) \
> VMLINUX_SYMBOL(__stop_kprobe_blacklist) = .;
> #else
>
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2014-05-02 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140417081705.26341.96719.stgit@ltc230.yrl.intra.hitachi.co.jp>
[not found] ` <tip-376e242429bf8539ef39a080ac113c8799840b13@git.kernel.org>
2014-05-01 5:26 ` kprobes broken in linux-next (was Re: [tip:perf/kprobes] kprobes: Introduce NOKPROBE_SYMBOL() macro to maintain kprobes blacklist) Vineet Gupta
2014-05-02 1:13 ` Masami Hiramatsu [this message]
2014-05-07 4:56 ` Vineet Gupta
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=5362F147.6030901@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=Anton.Kolesov@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=akataria@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=arnd@arndb.de \
--cc=chrisw@sous-sol.org \
--cc=davem@davemloft.net \
--cc=dl9pf@gmx.de \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=sparse@chrisli.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).