Hello,
syzbot hit the following crash on net-next commit
fb66cb0775609852b812c9bc2bd1589374317410 (Wed Feb 28 14:54:54 2018 +0000)
Merge tag 'mlx5-updates-2018-02-23' of
git://
git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output is attached.
compiler: gcc (GCC) 7.1.1 20170620
.config is attached.
CC: [
da...@davemloft.net kuz...@ms2.inr.ac.ru linux-...@vger.kernel.org
net...@vger.kernel.org yosh...@linux-ipv6.org]
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+cf0495...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.
WARNING: CPU: 1 PID: 12318 at kernel/locking/lockdep.c:700
arch_local_save_flags kernel/locking/lockdep.c:720 [inline]
WARNING: CPU: 1 PID: 12318 at kernel/locking/lockdep.c:700
look_up_lock_class kernel/locking/lockdep.c:691 [inline]
WARNING: CPU: 1 PID: 12318 at kernel/locking/lockdep.c:700
register_lock_class+0x1591/0x2820 kernel/locking/lockdep.c:750
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 12318 Comm: syz-executor2 Not tainted 4.16.0-rc2+ #245
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x194/0x24d lib/dump_stack.c:53
panic+0x1e4/0x41c kernel/panic.c:183
__warn+0x1dc/0x200 kernel/panic.c:547
report_bug+0x211/0x2d0 lib/bug.c:184
fixup_bug.part.11+0x37/0x80 arch/x86/kernel/traps.c:178
fixup_bug arch/x86/kernel/traps.c:247 [inline]
do_error_trap+0x2d7/0x3e0 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:315
invalid_op+0x58/0x80 arch/x86/entry/entry_64.S:957
RIP: 0010:arch_local_save_flags kernel/locking/lockdep.c:720 [inline]
RIP: 0010:look_up_lock_class kernel/locking/lockdep.c:691 [inline]
RIP: 0010:register_lock_class+0x1591/0x2820 kernel/locking/lockdep.c:750
RSP: 0018:ffff8801b5e86db8 EFLAGS: 00010087
RAX: 0000000000000004 RBX: 1ffff10036bd0dc9 RCX: 1ffffffff10ba860
RDX: ffffffff8683b840 RSI: 1ffffffff1028bb0 RDI: ffff8801c5659338
RBP: ffff8801b5e871d0 R08: 0000000000000003 R09: ffff8801c5659320
R10: 0000000000000000 R11: ffff8801c5659320 R12: 0000000000000000
R13: 0000000000000000 R14: ffffffff88145d60 R15: ffffffff8691bae0
__lock_acquire+0x1de/0x3e00 kernel/locking/lockdep.c:3319
lock_acquire+0x1d5/0x580 kernel/locking/lockdep.c:3920
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x31/0x40 kernel/locking/spinlock.c:168
spin_lock_bh include/linux/spinlock.h:315 [inline]
lock_sock_nested+0x44/0x110 net/core/sock.c:2773
lock_sock include/net/sock.h:1464 [inline]
do_ip_getsockopt+0x1b3/0x2170 net/ipv4/ip_sockglue.c:1331
ip_getsockopt+0x90/0x200 net/ipv4/ip_sockglue.c:1562
udp_getsockopt+0x45/0x80 net/ipv4/udp.c:2478
sock_common_getsockopt+0x95/0xd0 net/core/sock.c:2938
SYSC_getsockopt net/socket.c:1881 [inline]
SyS_getsockopt+0x178/0x340 net/socket.c:1863
do_syscall_64+0x280/0x940 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x453d69
RSP: 002b:00007f3b3e8c0c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000037
RAX: ffffffffffffffda RBX: 00007f3b3e8c16d4 RCX: 0000000000453d69
RDX: 000000000000002d RSI: 0000000000000000 RDI: 0000000000000017
RBP: 000000000072bf58 R08: 0000000020000040 R09: 0000000000000000
R10: 0000000020000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000000000f8 R14: 00000000006f17e0 R15: 0000000000000001
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This bug is generated by a dumb bot. It may contain errors.
See
https://goo.gl/tpsmEJ for details.
Direct all questions to
syzk...@googlegroups.com.
syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream