From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, rusty@rustcorp.com.au,
ananth@in.ibm.com, fweisbec@gmail.com, rostedt@goodmis.org,
jbeulich@novell.com, tglx@linutronix.de, jbaron@redhat.com,
mhiramat@redhat.com, mingo@elte.hu,
linux-tip-commits@vger.kernel.org,
2nddept-manager@sdl.hitachi.co.jp
Subject: Re: [tip:perf/core] x86: Introduce text_poke_smp_batch() for batch-code modifying
Date: Mon, 14 Feb 2011 10:25:04 +0900 [thread overview]
Message-ID: <4D588470.2040307@hitachi.com> (raw)
In-Reply-To: <1297458466.5226.93.camel@laptop>
(2011/02/12 6:07), Peter Zijlstra wrote:
> On Mon, 2010-12-06 at 18:17 +0000, tip-bot for Masami Hiramatsu wrote:
>
>> @@ -631,10 +639,13 @@ static int __kprobes stop_machine_text_poke(void *data)
>> void *__kprobes text_poke_smp(void *addr, const void *opcode, size_t len)
>> {
>> struct text_poke_params tpp;
>> + struct text_poke_param p;
>>
>> - tpp.addr = addr;
>> - tpp.opcode = opcode;
>> - tpp.len = len;
>> + p.addr = addr;
>> + p.opcode = opcode;
>> + p.len = len;
>> + tpp.params = &p;
>> + tpp.nparams = 1;
>> atomic_set(&stop_machine_first, 1);
>> wrote_text = 0;
>> /* Use __stop_machine() because the caller already got online_cpus. */
>
> ^^^^^^^^^
>
>> @@ -642,6 +653,26 @@ void *__kprobes text_poke_smp(void *addr, const void *opcode, size_t len)
>> return addr;
>> }
>>
>> +/**
>> + * text_poke_smp_batch - Update instructions on a live kernel on SMP
>> + * @params: an array of text_poke parameters
>> + * @n: the number of elements in params.
>> + *
>> + * Modify multi-byte instruction by using stop_machine() on SMP. Since the
>> + * stop_machine() is heavy task, it is better to aggregate text_poke requests
>> + * and do it once if possible.
>> + *
>> + * Note: Must be called under get_online_cpus() and text_mutex.
>> + */
>> +void __kprobes text_poke_smp_batch(struct text_poke_param *params, int n)
>> +{
>> + struct text_poke_params tpp = {.params = params, .nparams = n};
>> +
>> + atomic_set(&stop_machine_first, 1);
>> + wrote_text = 0;
>> + stop_machine(stop_machine_text_poke, (void *)&tpp, NULL);
>> +}
>
> ^^^^^^^^^^^^^^
Oops! Indeed, it's my mistake.
Thank you for reporting & fixing!
>
>
> ---
> Subject: x86: Fix text_poke_smp_batch() deadlock
>
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> 2.6.38-rc4-test+ #1
> -------------------------------------------------------
> bash/1850 is trying to acquire lock:
> (text_mutex){+.+.+.}, at: [<ffffffff8100a9c1>] return_to_handler+0x0/0x2f
>
> but task is already holding lock:
> (smp_alt){+.+...}, at: [<ffffffff8100a9c1>] return_to_handler+0x0/0x2f
>
> which lock already depends on the new lock.
>
>
> the existing dependency chain (in reverse order) is:
>
> -> #2 (smp_alt){+.+...}:
> [<ffffffff81082d02>] lock_acquire+0xcd/0xf8
> [<ffffffff8192e119>] __mutex_lock_common+0x4c/0x339
> [<ffffffff8192e4ca>] mutex_lock_nested+0x3e/0x43
> [<ffffffff8101050f>] alternatives_smp_switch+0x77/0x1d8
> [<ffffffff81926a6f>] do_boot_cpu+0xd7/0x762
> [<ffffffff819277dd>] native_cpu_up+0xe6/0x16a
> [<ffffffff81928e28>] _cpu_up+0x9d/0xee
> [<ffffffff81928f4c>] cpu_up+0xd3/0xe7
> [<ffffffff82268d4b>] kernel_init+0xe8/0x20a
> [<ffffffff8100ba24>] kernel_thread_helper+0x4/0x10
>
> -> #1 (cpu_hotplug.lock){+.+.+.}:
> [<ffffffff81082d02>] lock_acquire+0xcd/0xf8
> [<ffffffff8192e119>] __mutex_lock_common+0x4c/0x339
> [<ffffffff8192e4ca>] mutex_lock_nested+0x3e/0x43
> [<ffffffff810568cc>] get_online_cpus+0x41/0x55
> [<ffffffff810a1348>] stop_machine+0x1e/0x3e
> [<ffffffff819314c1>] text_poke_smp_batch+0x3a/0x3c
> [<ffffffff81932b6c>] arch_optimize_kprobes+0x10d/0x11c
> [<ffffffff81933a51>] kprobe_optimizer+0x152/0x222
> [<ffffffff8106bb71>] process_one_work+0x1d3/0x335
> [<ffffffff8106cfae>] worker_thread+0x104/0x1a4
> [<ffffffff810707c4>] kthread+0x9d/0xa5
> [<ffffffff8100ba24>] kernel_thread_helper+0x4/0x10
>
> -> #0 (text_mutex){+.+.+.}:
>
>
> other info that might help us debug this:
>
> 6 locks held by bash/1850:
> #0: (&buffer->mutex){+.+.+.}, at: [<ffffffff8100a9c1>] return_to_handler+0x0/0x2f
> #1: (s_active#75){.+.+.+}, at: [<ffffffff8100a9c1>] return_to_handler+0x0/0x2f
> #2: (x86_cpu_hotplug_driver_mutex){+.+.+.}, at: [<ffffffff8100a9c1>] return_to_handler+0x0/0x2f
> #3: (cpu_add_remove_lock){+.+.+.}, at: [<ffffffff8100a9c1>] return_to_handler+0x0/0x2f
> #4: (cpu_hotplug.lock){+.+.+.}, at: [<ffffffff8100a9c1>] return_to_handler+0x0/0x2f
> #5: (smp_alt){+.+...}, at: [<ffffffff8100a9c1>] return_to_handler+0x0/0x2f
>
> stack backtrace:
> Pid: 1850, comm: bash Not tainted 2.6.38-rc4-test+ #1
> Call Trace:
>
> [<ffffffff81080eb2>] print_circular_bug+0xa8/0xb7
> [<ffffffff8192e4ca>] mutex_lock_nested+0x3e/0x43
> [<ffffffff81010302>] alternatives_smp_unlock+0x3d/0x93
> [<ffffffff81010630>] alternatives_smp_switch+0x198/0x1d8
> [<ffffffff8102568a>] native_cpu_die+0x65/0x95
> [<ffffffff818cc4ec>] _cpu_down+0x13e/0x202
> [<ffffffff8117a619>] sysfs_write_file+0x108/0x144
> [<ffffffff8111f5a2>] vfs_write+0xac/0xff
> [<ffffffff8111f7a9>] sys_write+0x4a/0x6e
>
> Reported-by: Steven Rostedt <rostedt@goodmis.org>
> Tested-by: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> ---
> arch/x86/kernel/alternative.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c
> index 1236085..7038b95 100644
> --- a/arch/x86/kernel/alternative.c
> +++ b/arch/x86/kernel/alternative.c
> @@ -671,7 +671,7 @@ void __kprobes text_poke_smp_batch(struct text_poke_param *params, int n)
>
> atomic_set(&stop_machine_first, 1);
> wrote_text = 0;
> - stop_machine(stop_machine_text_poke, (void *)&tpp, NULL);
> + __stop_machine(stop_machine_text_poke, (void *)&tpp, NULL);
> }
>
> #if defined(CONFIG_DYNAMIC_FTRACE) || defined(HAVE_JUMP_LABEL)
>
--
Masami HIRAMATSU
2nd Dept. Linux Technology Center
Hitachi, Ltd., Systems Development Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2011-02-14 1:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 9:53 [PATCH -tip v5 0/8] Kprobes/x86: Batch optimization support Masami Hiramatsu
2010-12-03 9:53 ` [PATCH -tip v5 1/8] [CLEANUP] kprobes: Rename old_p to more appropriate name Masami Hiramatsu
2010-12-06 18:15 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-12-03 9:53 ` [PATCH -tip v5 2/8] [CLEANUP]kprobes: Cleanup disabling and unregistering path Masami Hiramatsu
2010-12-06 18:16 ` [tip:perf/core] kprobes: " tip-bot for Masami Hiramatsu
2010-12-03 9:54 ` [PATCH -tip v5 3/8] [CLEANUP]kprobes: Separate kprobe optimizing code from optimizer Masami Hiramatsu
2010-12-06 18:16 ` [tip:perf/core] kprobes: " tip-bot for Masami Hiramatsu
2010-12-03 9:54 ` [PATCH -tip v5 4/8] kprobes: Support delayed unoptimizing Masami Hiramatsu
2010-12-06 18:16 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-12-03 9:54 ` [PATCH -tip v5 5/8] kprobes: Reuse unused kprobe Masami Hiramatsu
2010-12-06 18:17 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-12-03 9:54 ` [PATCH -tip v5 6/8] x86: Introduce text_poke_smp_batch() for batch-code modifying Masami Hiramatsu
2010-12-03 14:44 ` Steven Rostedt
2010-12-06 18:17 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2011-02-11 21:07 ` Peter Zijlstra
2011-02-12 1:36 ` [tip:perf/urgent] x86: Fix text_poke_smp_batch() deadlock tip-bot for Peter Zijlstra
2011-02-14 1:25 ` Masami Hiramatsu [this message]
2010-12-03 9:54 ` [PATCH -tip v5 7/8] kprobes: Use text_poke_smp_batch for optimizing Masami Hiramatsu
2010-12-06 18:17 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-12-03 9:54 ` [PATCH -tip v5 8/8] kprobes: Use text_poke_smp_batch for unoptimizing Masami Hiramatsu
2010-12-06 18:18 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
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=4D588470.2040307@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=2nddept-manager@sdl.hitachi.co.jp \
--cc=ananth@in.ibm.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
/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