From: syzbot <syzbot+c58fa3b1231d2ea0c4d3@syzkaller.appspotmail.com>
To: bp@alien8.de, douly.fnst@cn.fujitsu.com, hpa@zytor.com,
konrad.wilk@oracle.com, len.brown@intel.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, puwen@hygon.cn, rppt@linux.vnet.ibm.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: general protection fault in __bfs (2)
Date: Tue, 22 Jan 2019 10:23:05 -0800 [thread overview]
Message-ID: <00000000000086d87305801011c4@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 133bbb18ab1a virtio-net: per-queue RPS config
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=130be6cf400000
kernel config: https://syzkaller.appspot.com/x/.config?x=8a4dffabfb4e36f9
dashboard link: https://syzkaller.appspot.com/bug?extid=c58fa3b1231d2ea0c4d3
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1244d4b7400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+c58fa3b1231d2ea0c4d3@syzkaller.appspotmail.com
Enabling of bearer <udp:syz0> rejected, already enabled
Enabling of bearer <udp:syz0> rejected, already enabled
Enabling of bearer <udp:syz0> rejected, already enabled
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 8646 Comm: syz-executor1 Not tainted 5.0.0-rc2+ #12
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:lock_accessed kernel/locking/lockdep.c:968 [inline]
RIP: 0010:__bfs kernel/locking/lockdep.c:1035 [inline]
RIP: 0010:__bfs+0x2ce/0x7a0 kernel/locking/lockdep.c:989
Code: 49 01 00 00 49 8d 7f 10 4c 89 f8 4c 8b 1d 7a d0 ee 09 48 89 f9 48 2d
20 47 32 8b 44 8b 15 ca ce 61 09 48 c1 e9 03 48 c1 f8 06 <42> 80 3c 21 00
0f 85 2c 03 00 00 49 8b 77 10 4c 8d 46 2c 4c 89 c1
RSP: 0018:ffff8880ae707110 EFLAGS: 00010003
RAX: 0000000001d336e3 RBX: ffffed1015ce0e3b RCX: 0000000000000002
RDX: 1ffff11015ce0e37 RSI: 0000000000000001 RDI: 0000000000000010
RBP: ffff8880ae707240 R08: 0000000000000001 R09: 1ffff11015ce0e3b
R10: 000000000000be6c R11: 0000000000001e64 R12: dffffc0000000000
R13: ffffffff8b200110 R14: ffff8880ae707218 R15: 0000000000000000
FS: 00007f29120d4700(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2912091db8 CR3: 000000008a5ae000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
__bfs_forwards kernel/locking/lockdep.c:1063 [inline]
find_usage_forwards kernel/locking/lockdep.c:1363 [inline]
check_usage_forwards+0x164/0x3e0 kernel/locking/lockdep.c:2575
mark_lock_irq kernel/locking/lockdep.c:2690 [inline]
mark_lock+0x519/0x1cd0 kernel/locking/lockdep.c:3062
mark_irqflags kernel/locking/lockdep.c:2940 [inline]
__lock_acquire+0x139c/0x4a30 kernel/locking/lockdep.c:3295
lock_acquire+0x1db/0x570 kernel/locking/lockdep.c:3841
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2f/0x40 kernel/locking/spinlock.c:144
spin_lock include/linux/spinlock.h:329 [inline]
__queue_work+0xbfc/0x1450 kernel/workqueue.c:1414
delayed_work_timer_fn+0x5d/0x90 kernel/workqueue.c:1500
call_timer_fn+0x254/0x900 kernel/time/timer.c:1325
expire_timers kernel/time/timer.c:1358 [inline]
__run_timers+0x4a2/0xd50 kernel/time/timer.c:1681
run_timer_softirq+0x52/0xb0 kernel/time/timer.c:1694
__do_softirq+0x30b/0xb11 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:373 [inline]
irq_exit+0x180/0x1d0 kernel/softirq.c:413
exiting_irq arch/x86/include/asm/apic.h:536 [inline]
smp_apic_timer_interrupt+0x1b7/0x760 arch/x86/kernel/apic/apic.c:1062
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:807
</IRQ>
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/paravirt.h:766
[inline]
RIP: 0010:console_unlock+0xd46/0x11e0 kernel/printk/printk.c:2416
Code: 48 c1 e8 03 80 3c 08 00 0f 85 d2 03 00 00 48 83 3d fe 95 2a 08 00 0f
84 b9 02 00 00 e8 33 14 1a 00 48 8b bd 10 ff ff ff 57 9d <0f> 1f 44 00 00
e9 5c ff ff ff e8 1b 14 1a 00 48 8b 7d 08 c7 05 7d
RSP: 0018:ffff8880a8c06ed8 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13
RAX: ffff88809741c3c0 RBX: 0000000000000200 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: ffffffff8167eabd RDI: 0000000000000293
RBP: ffff8880a8c06ff8 R08: 0000000000000006 R09: ffff88809741ccd8
R10: ffff88809741c3c0 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff849d5d60 R14: ffffffff89f76fd0 R15: 0000000000006801
vprintk_emit+0x370/0x960 kernel/printk/printk.c:1931
vprintk_default+0x28/0x30 kernel/printk/printk.c:1958
vprintk_func+0x7e/0x189 kernel/printk/printk_safe.c:398
printk+0xba/0xed kernel/printk/printk.c:1991
tipc_enable_bearer+0x498/0xed0 net/tipc/bearer.c:339
__tipc_nl_bearer_enable+0x389/0x4b0 net/tipc/bearer.c:899
tipc_nl_bearer_enable+0x23/0x40 net/tipc/bearer.c:907
genl_family_rcv_msg+0x80d/0x11a0 net/netlink/genetlink.c:601
genl_rcv_msg+0xca/0x16c net/netlink/genetlink.c:626
netlink_rcv_skb+0x17d/0x410 net/netlink/af_netlink.c:2477
genl_rcv+0x29/0x40 net/netlink/genetlink.c:637
netlink_unicast_kernel net/netlink/af_netlink.c:1310 [inline]
netlink_unicast+0x574/0x770 net/netlink/af_netlink.c:1336
netlink_sendmsg+0xa05/0xf90 net/netlink/af_netlink.c:1917
sock_sendmsg_nosec net/socket.c:621 [inline]
sock_sendmsg+0xdd/0x130 net/socket.c:631
___sys_sendmsg+0x7ec/0x910 net/socket.c:2116
__sys_sendmsg+0x112/0x270 net/socket.c:2154
__do_sys_sendmsg net/socket.c:2163 [inline]
__se_sys_sendmsg net/socket.c:2161 [inline]
__x64_sys_sendmsg+0x78/0xb0 net/socket.c:2161
do_syscall_64+0x1a3/0x800 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x458099
Code: 6d b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 3b b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f29120d3c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000458099
RDX: 0000000000000004 RSI: 0000000020000000 RDI: 0000000000000008
RBP: 000000000073bfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f29120d46d4
R13: 00000000004c53b4 R14: 00000000004d8f98 R15: 00000000ffffffff
Modules linked in:
---[ end trace 1d5ecf1214646bac ]---
RIP: 0010:lock_accessed kernel/locking/lockdep.c:968 [inline]
RIP: 0010:__bfs kernel/locking/lockdep.c:1035 [inline]
RIP: 0010:__bfs+0x2ce/0x7a0 kernel/locking/lockdep.c:989
Code: 49 01 00 00 49 8d 7f 10 4c 89 f8 4c 8b 1d 7a d0 ee 09 48 89 f9 48 2d
20 47 32 8b 44 8b 15 ca ce 61 09 48 c1 e9 03 48 c1 f8 06 <42> 80 3c 21 00
0f 85 2c 03 00 00 49 8b 77 10 4c 8d 46 2c 4c 89 c1
RSP: 0018:ffff8880ae707110 EFLAGS: 00010003
RAX: 0000000001d336e3 RBX: ffffed1015ce0e3b RCX: 0000000000000002
RDX: 1ffff11015ce0e37 RSI: 0000000000000001 RDI: 0000000000000010
RBP: ffff8880ae707240 R08: 0000000000000001 R09: 1ffff11015ce0e3b
R10: 000000000000be6c R11: 0000000000001e64 R12: dffffc0000000000
R13: ffffffff8b200110 R14: ffff8880ae707218 R15: 0000000000000000
FS: 00007f29120d4700(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2912091db8 CR3: 000000008a5ae000 CR4: 00000000001406e0
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
next reply other threads:[~2019-01-22 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 18:23 syzbot [this message]
2019-02-07 3:42 ` general protection fault in __bfs (2) syzbot
2019-03-11 13:27 ` syzbot
2019-03-11 13:49 ` Andy Shevchenko
2019-03-11 13:49 ` Andy Shevchenko
2019-03-28 16:47 ` Linus Walleij
2019-03-28 16:47 ` Linus Walleij
2020-06-18 22:52 ` syzbot
2020-06-19 12:17 ` Petr Machata
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=00000000000086d87305801011c4@google.com \
--to=syzbot+c58fa3b1231d2ea0c4d3@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=puwen@hygon.cn \
--cc=rppt@linux.vnet.ibm.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.