public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Peter Moody <pmoody@google.com>
Cc: ananth@in.ibm.com, anil.s.keshavamurthy@intel.com,
	davem@davemloft.net, linux-kernel@vger.kernel.org,
	Kees Cook <keescook@google.com>
Subject: Re: splat in kretprobe in get_task_mm(current)
Date: Wed, 04 Jun 2014 17:03:47 +0900	[thread overview]
Message-ID: <538ED2E3.1000707@hitachi.com> (raw)
In-Reply-To: <r3nfvjld5il.fsf@perdido.sfo.corp.google.com>

Hi Peter,

(2014/06/04 6:53), Peter Moody wrote:
> 
> As a follow up, I can reliably reproduce this bug with the following code
> 
> #include <unistd.h>
> #include <sys/types.h>
> 
> int main(int argc, char *argv[]) {
>   char *envp_[] = {NULL};
>   char *argv_[] = {argv[0]};
>   execve(argv[0], argv_, envp_);
>   return 0;
> }
> 
> run in parallel like so:
> 
> $ for x in $(seq 0 32) ; do ./a.out & done
> 
> giving me the following splat:.

Thank you for reporting that. I've tried to reproduce it with your code, but
not succeeded yet. Could you share us your kernel config too?

Thank you again,

> 
> [ 133.627336] BUG: spinlock cpu recursion on CPU#4, a.out/4643
> [ 133.627346]  lock: kretprobe_table_locks+0x1b80/0x2000, .magic: dead4ead, .owner: a.out/4630, .owner_cpu: 4
> [ 133.627350] CPU: 4 PID: 4643 Comm: a.out Tainted: G          IOE 3.15.0-rc8-splat+ #14
> [ 133.627351] Hardware name: Dell Inc. Precision WorkStation T3500  /09KPNV, BIOS A10 01/21/2011
> [ 133.627353]  ffff8804d5ae0000 ffff8804a7b4fd48 ffffffff81773413 0000000000000007
> [ 133.627358]  ffffffff82843600 ffff8804a7b4fd68 ffffffff8176ec74 ffffffff82843600
> [ 133.627362]  ffffffff81a8b6a6 ffff8804a7b4fd88 ffffffff8176ec9f ffffffff82843600
> [ 133.627366] Call Trace:
> [ 133.627372]  [<ffffffff81773413>] dump_stack+0x46/0x58
> [ 133.627376]  [<ffffffff8176ec74>] spin_dump+0x8f/0x94
> [ 133.627379]  [<ffffffff8176ec9f>] spin_bug+0x26/0x2b
> [ 133.627384]  [<ffffffff810c4195>] do_raw_spin_lock+0x105/0x190
> [ 133.627389]  [<ffffffff8177c7c0>] _raw_spin_lock_irqsave+0x70/0x90
> [ 133.627394]  [<ffffffff817839dc>] ? kretprobe_hash_lock+0x6c/0x80
> [ 133.627398]  [<ffffffff8177a86e>] ? mutex_unlock+0xe/0x10
> [ 133.627401]  [<ffffffff817839dc>] kretprobe_hash_lock+0x6c/0x80
> [ 133.627404]  [<ffffffff8177f16d>] trampoline_handler+0x3d/0x220
> [ 133.627407]  [<ffffffff8177f0fe>] kretprobe_trampoline+0x25/0x57
> [ 133.627412]  [<ffffffff811e28e8>] ? do_execve+0x18/0x20
> [ 133.627415]  [<ffffffff817862a9>] stub_execve+0x69/0xa0
> 


-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com



  reply	other threads:[~2014-06-04  8:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 17:39 splat in kretprobe in get_task_mm(current) Peter Moody
2014-06-03 21:53 ` Peter Moody
2014-06-04  8:03   ` Masami Hiramatsu [this message]
2014-06-04 14:07     ` Masami Hiramatsu
2014-06-04 15:23       ` Peter Moody
2014-06-04 22:49         ` Masami Hiramatsu
2014-06-04 23:00           ` Peter Moody
2014-06-04 16:05       ` (ltc-kernel 9473) " 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=538ED2E3.1000707@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=keescook@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmoody@google.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