kernel BUG at net/packet/af_packet.c:LINE!

[syzbot]

Hello,

syzkaller hit the following crash on
9829d9f31f6c0e4984545e03032f14ccca6eeb68
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.
C reproducer is attached
syzkaller reproducer is attached. See https://goo.gl/kgGztJ
for information about syzkaller reproducers
CC: [andre...@google.com anoob...@citrix.com da...@davemloft.net
edum...@google.com elena.r...@intel.com ja...@ovn.org
kees...@chromium.org linux-...@vger.kernel.org mal...@google.com
net...@vger.kernel.org rami....@intel.com sowmini....@oracle.com
wil...@google.com]

kernel BUG at net/packet/af_packet.c:1521!
invalid opcode: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 8837 Comm: syzkaller121704 Not tainted 4.13.0-next-20170904+ #14
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff8801c28e4200 task.stack: ffff8801c2f10000
RIP: 0010:__fanout_unlink net/packet/af_packet.c:1521 [inline]
RIP: 0010:__unregister_prot_hook+0x139/0x280 net/packet/af_packet.c:367
RSP: 0018:ffff8801c2f17700 EFLAGS: 00010297
RAX: ffff8801c28e4200 RBX: ffff8801c328e980 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff84d40ec1 RDI: ffff8801c295c308
RBP: ffff8801c2f17740 R08: ffff8801c2f17050 R09: ffff8801c2f17048
R10: ffff8801c2f16fc0 R11: 1ffff1003851cad3 R12: ffff8801c295c300
R13: ffff8801c328e980 R14: 0000000000000000 R15: ffff8801c2f17d70
FS: 00007fa4f7af7700(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000208e3000 CR3: 00000001cfdf3000 CR4: 00000000001406f0
Call Trace:
packet_set_ring+0xe7c/0x1b70 net/packet/af_packet.c:4305
packet_setsockopt+0x6cd/0x1e80 net/packet/af_packet.c:3660
SYSC_setsockopt net/socket.c:1852 [inline]
SyS_setsockopt+0x189/0x360 net/socket.c:1831
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x445d39
RSP: 002b:00007fa4f7af6dc8 EFLAGS: 00000202 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000445d39
RDX: 0000000000000005 RSI: 0000000000000107 RDI: 0000000000000004
RBP: 0000000000000082 R08: 000000000000047e R09: 00007fa4f7af7700
R10: 0000000020001000 R11: 0000000000000202 R12: 0000000000000000
R13: 00007ffe31674eaf R14: 00007fa4f7af79c0 R15: 0000000000000000
Code: 48 89 fa 48 c1 ea 03 42 80 3c 3a 00 0f 85 4e 01 00 00 4d 3b 6c c4 28
74 16 83 c3 01 e8 f1 17 2d fd 44 39 f3 75 cd e8 e7 17 2d fd <0f> 0b 31 c0
41 8d 5e ff 48 89 45 c0 e8 d6 17 2d fd 49 8d 7c dc
RIP: __fanout_unlink net/packet/af_packet.c:1521 [inline] RSP:
ffff8801c2f17700
RIP: __unregister_prot_hook+0x139/0x280 net/packet/af_packet.c:367 RSP:
ffff8801c2f17700
---[ end trace 5ca9d00baeae474d ]---
Kernel panic - not syncing: Fatal exception
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.
Please credit me with: Reported-by: syzbot <syzk...@googlegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is committed, 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.
To upstream this report, please reply with:
#syz upstream

[Dmitry Vyukov]

This seem to have been fixed already, reproducers don't work

#syz invalid


On Wed, Nov 1, 2017 at 9:14 PM, syzbot
<bot+907de6144b83bd17cc...@syzkaller.appspotmail.com>
wrote:

> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/94eb2c0495828705ca055cefd727%40google.com.
> For more options, visit https://groups.google.com/d/optout.