Date:   Sun, 17 Dec 2017 23:40:01 -0800
From:   syzbot 
        <bot+37ebea780f9dd19bfe677a5a84c440ed34d396df@...kaller.appspotmail.com>
To:     Jason@...c4.com, adobriyan@...il.com, davem@...emloft.net,
        dsa@...ulusnetworks.com, edumazet@...gle.com,
        elena.reshetova@...el.com, fw@...len.de, idosch@...lanox.com,
        ihrachys@...hat.com, ishkamiel@...il.com, keescook@...omium.org,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        roopa@...ulusnetworks.com, sowmini.varadhan@...cle.com,
        syzkaller-bugs@...glegroups.com
Subject: INFO: trying to register non-static key in neigh_flush_dev

Hello,

syzkaller hit the following crash on  
6084b576dca2e898f5c101baef151f7bfdbb606d
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

Unfortunately, I don't have any reproducer for this bug yet.


device lo left promiscuous mode
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 1 PID: 8926 Comm: syz-executor4 Not tainted 4.15.0-rc3-next-20171214+  
#67
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+0xe9/0x14b lib/dump_stack.c:53
  register_lock_class+0x164/0x5d0 kernel/locking/lockdep.c:752
  __lock_acquire+0xb4/0x1430 kernel/locking/lockdep.c:3314
  lock_acquire+0xbf/0x220 kernel/locking/lockdep.c:3914
  __raw_write_lock include/linux/rwlock_api_smp.h:210 [inline]
  _raw_write_lock+0x2a/0x40 kernel/locking/spinlock.c:288
  neigh_flush_dev+0x1b1/0x330 net/core/neighbour.c:253
  neigh_changeaddr+0x2f/0x40 net/core/neighbour.c:285
  arp_netdev_event+0x73/0x90 net/ipv4/arp.c:1252
  notifier_call_chain+0x41/0xc0 kernel/notifier.c:93
  __raw_notifier_call_chain kernel/notifier.c:394 [inline]
  raw_notifier_call_chain+0x2d/0x40 kernel/notifier.c:401
  call_netdevice_notifiers_info+0x32/0x60 net/core/dev.c:1679
  __dev_notify_flags+0x12a/0x130 net/core/dev.c:6888
  dev_change_flags+0x5e/0x70 net/core/dev.c:6910
  devinet_ioctl+0x77b/0x930 net/ipv4/devinet.c:1083
  inet_ioctl+0xda/0x130 net/ipv4/af_inet.c:902
  sock_do_ioctl+0x2c/0x60 net/socket.c:964
  sock_ioctl+0x211/0x320 net/socket.c:1061
  vfs_ioctl fs/ioctl.c:46 [inline]
  do_vfs_ioctl+0xaf/0x840 fs/ioctl.c:686
  SYSC_ioctl fs/ioctl.c:701 [inline]
  SyS_ioctl+0x8f/0xc0 fs/ioctl.c:692
  entry_SYSCALL_64_fastpath+0x1f/0x96
RIP: 0033:0x452a09
RSP: 002b:00007f8629f4bc58 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000071bea0 RCX: 0000000000452a09
RDX: 0000000020915fe0 RSI: 0000000000008914 RDI: 0000000000000016
RBP: 0000000000000020 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000212 R12: 00000000006ed3a0
R13: 00000000ffffffff R14: 00007f8629f4c6d4 R15: 0000000000000000
BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
IP: neigh_cleanup_and_release+0x13/0x70 net/core/neighbour.c:100
PGD 1e5fc5067 P4D 1e5fc5067 PUD 1e5fc4067 PMD 0
Oops: 0000 [#1] SMP
Dumping ftrace buffer:
    (ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 8926 Comm: syz-executor4 Not tainted 4.15.0-rc3-next-20171214+  
#67
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
RIP: 0010:neigh_cleanup_and_release+0x13/0x70 net/core/neighbour.c:100
RSP: 0018:ffffc90000d8bb58 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff8801e3bb9800 RCX: ffffffff820e511f
RDX: 0000000000010000 RSI: ffffc90003855000 RDI: ffff8801e3bb9800
RBP: ffffc90000d8bb68 R08: 0000000000000000 R09: ffffffff820e5421
R10: ffffc90000d8bae8 R11: 0000000000000000 R12: ffff8801e3804370
R13: ffff8801e39ba000 R14: ffff8801e39ba000 R15: ffffffff831705f0
FS:  00007f8629f4c700(0000) GS:ffff88021fd00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000028 CR3: 00000001e4b42001 CR4: 00000000001606e0
DR0: 0000000020000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
  neigh_flush_dev+0x270/0x330 net/core/neighbour.c:277
  neigh_changeaddr+0x2f/0x40 net/core/neighbour.c:285
  arp_netdev_event+0x73/0x90 net/ipv4/arp.c:1252
  notifier_call_chain+0x41/0xc0 kernel/notifier.c:93
  __raw_notifier_call_chain kernel/notifier.c:394 [inline]
  raw_notifier_call_chain+0x2d/0x40 kernel/notifier.c:401
  call_netdevice_notifiers_info+0x32/0x60 net/core/dev.c:1679
  __dev_notify_flags+0x12a/0x130 net/core/dev.c:6888
  dev_change_flags+0x5e/0x70 net/core/dev.c:6910
  devinet_ioctl+0x77b/0x930 net/ipv4/devinet.c:1083
  inet_ioctl+0xda/0x130 net/ipv4/af_inet.c:902
  sock_do_ioctl+0x2c/0x60 net/socket.c:964
  sock_ioctl+0x211/0x320 net/socket.c:1061
  vfs_ioctl fs/ioctl.c:46 [inline]
  do_vfs_ioctl+0xaf/0x840 fs/ioctl.c:686
  SYSC_ioctl fs/ioctl.c:701 [inline]
  SyS_ioctl+0x8f/0xc0 fs/ioctl.c:692
  entry_SYSCALL_64_fastpath+0x1f/0x96
RIP: 0033:0x452a09
RSP: 002b:00007f8629f4bc58 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000071bea0 RCX: 0000000000452a09
RDX: 0000000020915fe0 RSI: 0000000000008914 RDI: 0000000000000016
RBP: 0000000000000020 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000212 R12: 00000000006ed3a0
R13: 00000000ffffffff R14: 00007f8629f4c6d4 R15: 0000000000000000
Code: 1e 00 00 00 e8 af f4 ff ff 5b 5d c3 66 90 66 2e 0f 1f 84 00 00 00 00  
00 55 48 89 e5 41 54 53 48 89 fb e8 21 52 1d ff 48 8b 43 10 <4c> 8b 60 28  
4d 85 e4 74 0b e8 0f 52 1d ff 48 89 df 41 ff d4 e8
RIP: neigh_cleanup_and_release+0x13/0x70 net/core/neighbour.c:100 RSP:  
ffffc90000d8bb58
CR2: 0000000000000028
---[ end trace f9e4938f6bf042cf ]---


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzkaller@...glegroups.com.
Please credit me with: Reported-by: syzbot <syzkaller@...glegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is merged into any tree, 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.

View attachment "config.txt" of type "text/plain" (126475 bytes)

Download attachment "raw.log" of type "application/octet-stream" (1048576 bytes)

Powered by blists - more mailing lists