linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+d8a8e42dfba0454286ff@syzkaller.appspotmail.com>
To: bigeasy@linutronix.de, linux-kernel@vger.kernel.org,
	matt@codeblueprint.co.uk, mingo@kernel.org, peterz@infradead.org,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: BUG: corrupted list in cpu_stop_queue_work
Date: Sun, 08 Jul 2018 19:30:02 -0700	[thread overview]
Message-ID: <000000000000693c7d057087caf3@google.com> (raw)
In-Reply-To: <00000000000032412205706753b5@google.com>

syzbot has found a reproducer for the following crash on:

HEAD commit:    526674536360 Add linux-next specific files for 20180706
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11ac81b2400000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c8d1cfc0cb798e48
dashboard link: https://syzkaller.appspot.com/bug?extid=d8a8e42dfba0454286ff
compiler:       gcc (GCC) 8.0.1 20180413 (experimental)
syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=1507ca2c400000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10431a2c400000

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

RBP: 00000000006cb018 R08: 0000000000000002 R09: 00007fff6f890032
R10: 0000000020377000 R11: 0000000000000246 R12: 0000000000000003
R13: ffffffffffffffff R14: 0000000000000000 R15: 0000000000000000
list_add corruption. prev->next should be next (ffff8801daf26708), but was  
0000000000000000. (prev=ffff8801daf26740).
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:28!
invalid opcode: 0000 [#1] SMP KASAN
CPU: 1 PID: 4449 Comm: syz-executor507 Not tainted  
4.18.0-rc3-next-20180706+ #1
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
RIP: 0010:__list_add_valid.cold.0+0x23/0x25 lib/list_debug.c:26
Code: e8 9f 72 57 fe eb 97 48 89 d9 48 c7 c7 60 80 1a 88 e8 72 b8 ff fd 0f  
0b 48 89 f1 48 c7 c7 20 81 1a 88 48 89 de e8 5e b8 ff fd <0f> 0b 4c 89 e2  
48 89 de 48 c7 c7 60 82 1a 88 e8 4a b8 ff fd 0f 0b
RSP: 0018:ffff8801daf079c0 EFLAGS: 00010086
RAX: 0000000000000075 RBX: ffff8801daf26708 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff81634381 RDI: 0000000000000001
RBP: ffff8801daf079d8 R08: ffff8801ad2464c0 R09: ffffed003b5e4fc0
R10: ffffed003b5e4fc0 R11: ffff8801daf27e07 R12: ffff8801daf26740
R13: ffff8801daf07ab8 R14: ffff8801daf26740 R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000203e8008 CR3: 0000000008e6a000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
  <IRQ>
  __list_add include/linux/list.h:60 [inline]
  list_add_tail include/linux/list.h:93 [inline]
  __cpu_stop_queue_work kernel/stop_machine.c:72 [inline]
  cpu_stop_queue_work+0x248/0x460 kernel/stop_machine.c:87
  stop_one_cpu_nowait+0xd3/0x100 kernel/stop_machine.c:341
  watchdog_timer_fn+0x93/0x2e0 kernel/watchdog.c:367
  __run_hrtimer kernel/time/hrtimer.c:1398 [inline]
  __hrtimer_run_queues+0x3eb/0x10c0 kernel/time/hrtimer.c:1460
  hrtimer_interrupt+0x2f3/0x750 kernel/time/hrtimer.c:1518
  local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1025 [inline]
  smp_apic_timer_interrupt+0x165/0x730 arch/x86/kernel/apic/apic.c:1050
  apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:867
  </IRQ>
RIP: 0010:__sanitizer_cov_trace_pc+0x0/0x50 kernel/kcov.c:146
Code: 14 dd 28 00 00 00 4d 39 d0 72 1b 49 83 c1 01 4a 89 7c 10 e0 4a 89 74  
10 e8 4a 89 54 10 f0 4a 89 4c d8 20 4c 89 08 5d c3 66 90 <55> 65 48 8b 04  
25 40 ee 01 00 65 8b 15 5f 73 85 7e 48 89 e5 81 e2
RSP: 0018:ffff8801ad79e208 EFLAGS: 00000292 ORIG_RAX: ffffffffffffff13
RAX: ffff8801ad2464c0 RBX: ffffea000701e000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff819b034f RDI: 0000000000000007
RBP: ffff8801ad79e5a8 R08: ffff8801ad2464c0 R09: fffff94000e03c06
R10: fffff94000e03c06 R11: ffffea000701e037 R12: ffff8801ad79e580
R13: 1ffff10035af3c68 R14: dffffc0000000000 R15: 0000000000000000
  shmem_undo_range+0x38e/0x29a0 mm/shmem.c:795
  shmem_truncate_range+0x27/0xa0 mm/shmem.c:971
  shmem_evict_inode+0x3b2/0xcb0 mm/shmem.c:1071
  evict+0x4ae/0x990 fs/inode.c:558
  iput_final fs/inode.c:1508 [inline]
  iput+0x635/0xaa0 fs/inode.c:1534
  dentry_unlink_inode+0x4ae/0x640 fs/dcache.c:377
  __dentry_kill+0x44c/0x7a0 fs/dcache.c:569
  dentry_kill+0xc9/0x5a0 fs/dcache.c:688
  dput.part.26+0x66b/0x7a0 fs/dcache.c:849
  dput+0x15/0x20 fs/dcache.c:831
  __fput+0x558/0x930 fs/file_table.c:235
  ____fput+0x15/0x20 fs/file_table.c:251
  task_work_run+0x1ec/0x2a0 kernel/task_work.c:113
  exit_task_work include/linux/task_work.h:22 [inline]
  do_exit+0x1b08/0x2750 kernel/exit.c:869
  do_group_exit+0x177/0x440 kernel/exit.c:972
  __do_sys_exit_group kernel/exit.c:983 [inline]
  __se_sys_exit_group kernel/exit.c:981 [inline]
  __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:981
  do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
  entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x43f0f8
Code: Bad RIP value.
RSP: 002b:00007fff6f8995b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000043f0f8
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004bf1e8 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 0000000020377000 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d1180 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
Dumping ftrace buffer:
    (ftrace buffer empty)
---[ end trace 599d79740552877c ]---
RIP: 0010:__list_add_valid.cold.0+0x23/0x25 lib/list_debug.c:26
Code: e8 9f 72 57 fe eb 97 48 89 d9 48 c7 c7 60 80 1a 88 e8 72 b8 ff fd 0f  
0b 48 89 f1 48 c7 c7 20 81 1a 88 48 89 de e8 5e b8 ff fd <0f> 0b 4c 89 e2  
48 89 de 48 c7 c7 60 82 1a 88 e8 4a b8 ff fd 0f 0b
RSP: 0018:ffff8801daf079c0 EFLAGS: 00010086
RAX: 0000000000000075 RBX: ffff8801daf26708 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff81634381 RDI: 0000000000000001
RBP: ffff8801daf079d8 R08: ffff8801ad2464c0 R09: ffffed003b5e4fc0
R10: ffffed003b5e4fc0 R11: ffff8801daf27e07 R12: ffff8801daf26740
R13: ffff8801daf07ab8 R14: ffff8801daf26740 R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000043f0ce CR3: 0000000008e6a000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


  reply	other threads:[~2018-07-09  2:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-07 11:46 BUG: corrupted list in cpu_stop_queue_work syzbot
2018-07-09  2:30 ` syzbot [this message]
2018-07-09 12:55   ` Tetsuo Handa
2018-07-09 13:32     ` Matthew Wilcox
2018-07-09 14:15       ` Tetsuo Handa
2018-07-09 14:24         ` Matthew Wilcox
2018-07-09 14:34           ` Tetsuo Handa

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=000000000000693c7d057087caf3@google.com \
    --to=syzbot+d8a8e42dfba0454286ff@syzkaller.appspotmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --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;
as well as URLs for NNTP newsgroup(s).