Messages in this thread | | | Date | Mon, 09 Jul 2018 04:59:02 -0700 | Subject | BUG: corrupted list in p9_conn_cancel | From | syzbot <> |
| |
Hello,
syzbot found the following crash on:
HEAD commit: ca04b3cca11a Merge tag 'armsoc-fixes' of git://git.kernel... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=132bb168400000 kernel config: https://syzkaller.appspot.com/x/.config?x=2ca6c7a31d407f86 dashboard link: https://syzkaller.appspot.com/bug?extid=ad0832746849421bba05 compiler: gcc (GCC) 8.0.1 20180413 (experimental) userspace arch: i386 syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=16c4c2c2400000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=165c81b2400000
IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+ad0832746849421bba05@syzkaller.appspotmail.com
list_del corruption, ffff880045022ee8->next is LIST_POISON1 (dead000000000100) ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:47! invalid opcode: 0000 [#1] SMP KASAN CPU: 0 PID: 26 Comm: kworker/0:2 Not tainted 4.18.0-rc3+ #40 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events p9_poll_workfn RIP: 0010:__list_del_entry_valid.cold.1+0x26/0x58 lib/list_debug.c:45 Code: 02 fe 0f 0b 4c 89 e2 48 89 de 48 c7 c7 a0 65 1a 88 e8 4a 6e 02 fe 0f 0b 4c 89 ea 48 89 de 48 c7 c7 40 65 1a 88 e8 36 6e 02 fe <0f> 0b 48 89 de 48 c7 c7 60 66 1a 88 e8 25 6e 02 fe 0f 0b 48 89 de RSP: 0018:ffff8801d9467318 EFLAGS: 00010282 RAX: 000000000000004e RBX: ffff880045022ee8 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff81631821 RDI: 0000000000000001 RBP: ffff8801d9467330 R08: ffff8801d94346c0 R09: ffffed003b5c4fc0 R10: ffffed003b5c4fc0 R11: ffff8801dae27e07 R12: dead000000000200 R13: dead000000000100 R14: ffff8801d9467388 R15: 1ffff1003b28ce9e FS: 0000000000000000(0000) GS:ffff8801dae00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000008064ed0 CR3: 0000000008e6a000 CR4: 00000000001406f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: __list_del_entry include/linux/list.h:117 [inline] list_del include/linux/list.h:125 [inline] p9_conn_cancel+0x8d6/0xd30 net/9p/trans_fd.c:224 p9_poll_mux net/9p/trans_fd.c:620 [inline] p9_poll_workfn+0x4b2/0x6d0 net/9p/trans_fd.c:1107 process_one_work+0xc73/0x1ba0 kernel/workqueue.c:2153 worker_thread+0x189/0x13c0 kernel/workqueue.c:2296 kthread+0x345/0x410 kernel/kthread.c:246 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:412 Modules linked in: Dumping ftrace buffer: (ftrace buffer empty) ---[ end trace 13d6ed0983a959b1 ]--- RIP: 0010:__list_del_entry_valid.cold.1+0x26/0x58 lib/list_debug.c:45 Code: 02 fe 0f 0b 4c 89 e2 48 89 de 48 c7 c7 a0 65 1a 88 e8 4a 6e 02 fe 0f 0b 4c 89 ea 48 89 de 48 c7 c7 40 65 1a 88 e8 36 6e 02 fe <0f> 0b 48 89 de 48 c7 c7 60 66 1a 88 e8 25 6e 02 fe 0f 0b 48 89 de RSP: 0018:ffff8801d9467318 EFLAGS: 00010282 RAX: 000000000000004e RBX: ffff880045022ee8 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff81631821 RDI: 0000000000000001 RBP: ffff8801d9467330 R08: ffff8801d94346c0 R09: ffffed003b5c4fc0 R10: ffffed003b5c4fc0 R11: ffff8801dae27e07 R12: dead000000000200 R13: dead000000000100 R14: ffff8801d9467388 R15: 1ffff1003b28ce9e FS: 0000000000000000(0000) GS:ffff8801dae00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000008064ed0 CR3: 0000000008e6a000 CR4: 00000000001406f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
--- 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#bug-status-tracking for how to communicate with syzbot. syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches
| |