All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+65cecdd27b726c261799@syzkaller.appspotmail.com>
To: bp@alien8.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
	luto@kernel.org, mingo@redhat.com,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	x86@kernel.org
Subject: INFO: rcu detected stall in corrupted (3)
Date: Fri, 29 Mar 2019 15:34:05 -0700	[thread overview]
Message-ID: <000000000000b08190058543449f@google.com> (raw)

Hello,

syzbot found the following crash on:

HEAD commit:    8c2ffd91 Linux 5.1-rc2
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15099d2b200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8dcdce25ea72bedf
dashboard link: https://syzkaller.appspot.com/bug?extid=65cecdd27b726c261799
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17d3c67d200000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11d4f317200000

Bisection is inconclusive: the bug happens on the oldest tested release.

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=111a358b200000
console output: https://syzkaller.appspot.com/x/log.txt?x=151a358b200000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+65cecdd27b726c261799@syzkaller.appspotmail.com

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 	Tasks blocked on level-0 rcu_node (CPUs 0-1): P8340
rcu: 	(detected by 1, t=10502 jiffies, g=5905, q=81)
syz-executor586 R  running task    27832  8340   8338 0x00000000
Call Trace:
  context_switch kernel/sched/core.c:2877 [inline]
  __schedule+0x817/0x1cc0 kernel/sched/core.c:3518
  preempt_schedule_common+0x4f/0xe0 kernel/sched/core.c:3642
  preempt_schedule+0x4b/0x60 kernel/sched/core.c:3668
  ___preempt_schedule+0x16/0x18
  __sched_setscheduler+0x12fb/0x1e70 kernel/sched/core.c:4398
  sched_setattr kernel/sched/core.c:4440 [inline]
  __do_sys_sched_setattr kernel/sched/core.c:4616 [inline]
  __se_sys_sched_setattr kernel/sched/core.c:4595 [inline]
  __x64_sys_sched_setattr+0x184/0x2b0 kernel/sched/core.c:4595
  do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
  entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4403c9
Code: 76 77 78 5d 20 5b 2d 6c 3c 68 6f 73 74 6c 69 73 74 3e 5d 20 5b 2d 73  
3c 64 6f 6d 61 69 6e 6c 69 73 74 3e 5d 0a 20 20 20 20 20 <20> 20 20 20 20  
20 20 20 20 20 20 5b 2d 66 3c 63 6f 6e 66 66 69 6c
RSP: 002b:00007ffea1a49298 EFLAGS: 00000246 ORIG_RAX: 000000000000013a
RAX: ffffffffffffffda RBX: 00007ffea1a49340 RCX: 00000000004403c9
RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000002b80 R09: 0000000000400d10
R10: 000000000000f8f8 R11: 0000000000000246 R12: 0000000000401c90
R13: 0000000000401d20 R14: 0000000000000000 R15: 0000000000000000
syz-executor586 R  running task    27832  8340   8338 0x00000000
Call Trace:
  context_switch kernel/sched/core.c:2877 [inline]
  __schedule+0x817/0x1cc0 kernel/sched/core.c:3518
  preempt_schedule_common+0x4f/0xe0 kernel/sched/core.c:3642
  preempt_schedule+0x4b/0x60 kernel/sched/core.c:3668
  ___preempt_schedule+0x16/0x18
  __sched_setscheduler+0x12fb/0x1e70 kernel/sched/core.c:4398
  sched_setattr kernel/sched/core.c:4440 [inline]
  __do_sys_sched_setattr kernel/sched/core.c:4616 [inline]
  __se_sys_sched_setattr kernel/sched/core.c:4595 [inline]
  __x64_sys_sched_setattr+0x184/0x2b0 kernel/sched/core.c:4595
  do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
  entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4403c9
Code: 76 77 78 5d 20 5b 2d 6c 3c 68 6f 73 74 6c 69 73 74 3e 5d 20 5b 2d 73  
3c 64 6f 6d 61 69 6e 6c 69 73 74 3e 5d 0a 20 20 20 20 20 <20> 20 20 20 20  
20 20 20 20 20 20 5b 2d 66 3c 63 6f 6e 66 66 69 6c
RSP: 002b:00007ffea1a49298 EFLAGS: 00000246 ORIG_RAX: 000000000000013a
RAX: ffffffffffffffda RBX: 00007ffea1a49340 RCX: 00000000004403c9
RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000002b80 R09: 0000000000400d10
R10: 000000000000f8f8 R11: 0000000000000246 R12: 0000000000401c90
R13: 0000000000401d20 R14: 0000000000000000 R15: 0000000000000000


---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches

             reply	other threads:[~2019-03-29 22:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 22:34 syzbot [this message]
2019-03-30  0:13 ` INFO: rcu detected stall in corrupted (3) Tetsuo Handa
2019-03-30  7:46   ` Thomas Gleixner
2019-03-30 10:40     ` Tetsuo Handa
2019-03-30 10:45       ` Borislav Petkov
2019-03-30 10:57         ` Tetsuo Handa
2019-03-30 11:09           ` Borislav Petkov
2019-03-30 14:07             ` Tetsuo Handa
2019-03-30 19:05               ` Borislav Petkov
2019-04-01  6:42             ` Juri Lelli

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=000000000000b08190058543449f@google.com \
    --to=syzbot+65cecdd27b726c261799@syzkaller.appspotmail.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.