general protection fault in hsr_check_carrier_and_operstate
10 views
Skip to first unread message
syzbot
Jan 8, 2020, 5:43:12 PM1/8/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 84f5ad46 Linux 4.14.162
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=126b2021e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2eeb394ad524f8c4
dashboard link: https://syzkaller.appspot.com/bug?extid=d63f588a6f64054e7d5b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+d63f58...@syzkaller.appspotmail.com
device bridge554 entered promiscuous mode
device bridge1253 left promiscuous mode
device bridge1255 entered promiscuous mode
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
Modules linked in:
CPU: 1 PID: 6529 Comm: syz-executor.4 Not tainted 4.14.162-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff88820e9520c0 task.stack: ffff88820e958000
RIP: 0010:hsr_check_carrier_and_operstate+0x3e/0x5e0
net/hsr/hsr_device.c:116
RSP: 0018:ffff88820e95ee90 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000004 RCX: ffffc9000b45f000
RDX: 0000000000000002 RSI: ffffffff866171fa RDI: ffff88803f499620
RBP: ffff88820e95eec8 R08: ffff88820e9520c0 R09: 0000000000000001
R10: 0000000000000000 R11: ffff88820e9520c0 R12: 0000000000000000
R13: ffff88820e9ac600 R14: 0000000000000010 R15: ffff88820ecb5380
FS: 00007f5d3bfe6700(0000) GS:ffff8880aed00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000718934 CR3: 0000000200806000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
hsr_netdev_notify+0xef/0x8f0 net/hsr/hsr_main.c:51
notifier_call_chain+0x111/0x1b0 kernel/notifier.c:93
__raw_notifier_call_chain kernel/notifier.c:394 [inline]
raw_notifier_call_chain+0x2e/0x40 kernel/notifier.c:401
call_netdevice_notifiers_info+0x56/0x70 net/core/dev.c:1671
netdev_state_change net/core/dev.c:1318 [inline]
netdev_state_change+0xbf/0xe0 net/core/dev.c:1312
do_setlink+0x23da/0x2c20 net/core/rtnetlink.c:2280
rtnl_newlink+0x11a7/0x1700 net/core/rtnetlink.c:2651
rtnetlink_rcv_msg+0x3da/0xb70 net/core/rtnetlink.c:4306
netlink_rcv_skb+0x14f/0x3c0 net/netlink/af_netlink.c:2432
rtnetlink_rcv+0x1d/0x30 net/core/rtnetlink.c:4318
netlink_unicast_kernel net/netlink/af_netlink.c:1286 [inline]
netlink_unicast+0x44d/0x650 net/netlink/af_netlink.c:1312
netlink_sendmsg+0x7c4/0xc60 net/netlink/af_netlink.c:1877
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xce/0x110 net/socket.c:656
___sys_sendmsg+0x70a/0x840 net/socket.c:2062
__sys_sendmsg+0xb9/0x140 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x2d/0x50 net/socket.c:2103
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45af49
RSP: 002b:00007f5d3bfe5c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045af49
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000004
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f5d3bfe66d4
R13: 00000000004ca9a0 R14: 00000000004e3d80 R15: 00000000ffffffff
Code: 10 e8 47 84 fb fa 4c 89 e7 be 04 00 00 00 e8 4a ac ff ff 4c 8d 70 10
49 89 c4 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00
0f 85 0d 05 00 00 48 b8 00 00 00 00 00 fc ff df 49
RIP: hsr_check_carrier_and_operstate+0x3e/0x5e0 net/hsr/hsr_device.c:116
RSP: ffff88820e95ee90
---[ end trace a3d50887a9ae70f2 ]---
---
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 syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following crash on:
HEAD commit: 84f5ad46 Linux 4.14.162
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=126b2021e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2eeb394ad524f8c4
dashboard link: https://syzkaller.appspot.com/bug?extid=d63f588a6f64054e7d5b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+d63f58...@syzkaller.appspotmail.com
device bridge554 entered promiscuous mode
device bridge1253 left promiscuous mode
device bridge1255 entered promiscuous mode
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
Modules linked in:
CPU: 1 PID: 6529 Comm: syz-executor.4 Not tainted 4.14.162-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff88820e9520c0 task.stack: ffff88820e958000
RIP: 0010:hsr_check_carrier_and_operstate+0x3e/0x5e0
net/hsr/hsr_device.c:116
RSP: 0018:ffff88820e95ee90 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000004 RCX: ffffc9000b45f000
RDX: 0000000000000002 RSI: ffffffff866171fa RDI: ffff88803f499620
RBP: ffff88820e95eec8 R08: ffff88820e9520c0 R09: 0000000000000001
R10: 0000000000000000 R11: ffff88820e9520c0 R12: 0000000000000000
R13: ffff88820e9ac600 R14: 0000000000000010 R15: ffff88820ecb5380
FS: 00007f5d3bfe6700(0000) GS:ffff8880aed00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000718934 CR3: 0000000200806000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
hsr_netdev_notify+0xef/0x8f0 net/hsr/hsr_main.c:51
notifier_call_chain+0x111/0x1b0 kernel/notifier.c:93
__raw_notifier_call_chain kernel/notifier.c:394 [inline]
raw_notifier_call_chain+0x2e/0x40 kernel/notifier.c:401
call_netdevice_notifiers_info+0x56/0x70 net/core/dev.c:1671
netdev_state_change net/core/dev.c:1318 [inline]
netdev_state_change+0xbf/0xe0 net/core/dev.c:1312
do_setlink+0x23da/0x2c20 net/core/rtnetlink.c:2280
rtnl_newlink+0x11a7/0x1700 net/core/rtnetlink.c:2651
rtnetlink_rcv_msg+0x3da/0xb70 net/core/rtnetlink.c:4306
netlink_rcv_skb+0x14f/0x3c0 net/netlink/af_netlink.c:2432
rtnetlink_rcv+0x1d/0x30 net/core/rtnetlink.c:4318
netlink_unicast_kernel net/netlink/af_netlink.c:1286 [inline]
netlink_unicast+0x44d/0x650 net/netlink/af_netlink.c:1312
netlink_sendmsg+0x7c4/0xc60 net/netlink/af_netlink.c:1877
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xce/0x110 net/socket.c:656
___sys_sendmsg+0x70a/0x840 net/socket.c:2062
__sys_sendmsg+0xb9/0x140 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x2d/0x50 net/socket.c:2103
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45af49
RSP: 002b:00007f5d3bfe5c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045af49
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000004
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f5d3bfe66d4
R13: 00000000004ca9a0 R14: 00000000004e3d80 R15: 00000000ffffffff
Code: 10 e8 47 84 fb fa 4c 89 e7 be 04 00 00 00 e8 4a ac ff ff 4c 8d 70 10
49 89 c4 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00
0f 85 0d 05 00 00 48 b8 00 00 00 00 00 fc ff df 49
RIP: hsr_check_carrier_and_operstate+0x3e/0x5e0 net/hsr/hsr_device.c:116
RSP: ffff88820e95ee90
---[ end trace a3d50887a9ae70f2 ]---
---
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 syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Jan 8, 2020, 6:56:12 PM1/8/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following crash on:
HEAD commit: 84f5ad46 Linux 4.14.162
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16be4d15e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b8a69ee00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+d63f58...@syzkaller.appspotmail.com
device bridge17 entered promiscuous mode
device bridge16 entered promiscuous mode
RAX: dffffc0000000000 RBX: 0000000000000004 RCX: ffff888086cb4c00
RDX: 0000000000000002 RSI: 0000000000000004 RDI: ffff8880997f9920
RBP: ffff88808bffeec8 R08: ffff888086cb4380 R09: 0000000000000001
R10: 0000000000000000 R11: ffff888086cb4380 R12: 0000000000000000
R13: ffff888080bfd500 R14: 0000000000000010 R15: ffff88808098b540
FS: 00007f391fdbc700(0000) GS:ffff8880aec00000(0000) knlGS:0000000000000000
RIP: 0033:0x446d89
RSP: 002b:00007f391fdbbdb8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00000000006dbc88 RCX: 0000000000446d89
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000009
RBP: 00000000006dbc80 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000000246 R12: 00000000006dbc8c
R13: 00007ffc0185f22f R14: 00007f391fdbc9c0 R15: 20c49ba5e353f7cf
---[ end trace 3a402e1c952e2ff2 ]---
HEAD commit: 84f5ad46 Linux 4.14.162
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=2eeb394ad524f8c4
dashboard link: https://syzkaller.appspot.com/bug?extid=d63f588a6f64054e7d5b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a12156e00000
dashboard link: https://syzkaller.appspot.com/bug?extid=d63f588a6f64054e7d5b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b8a69ee00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+d63f58...@syzkaller.appspotmail.com
device bridge16 entered promiscuous mode
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
Modules linked in:
CPU: 0 PID: 7558 Comm: syz-executor124 Not tainted 4.14.162-syzkaller #0
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff888086cb4380 task.stack: ffff88808bff8000
Google 01/01/2011
RIP: 0010:hsr_check_carrier_and_operstate+0x3e/0x5e0
net/hsr/hsr_device.c:116
RSP: 0018:ffff88808bffee90 EFLAGS: 00010202
net/hsr/hsr_device.c:116
RAX: dffffc0000000000 RBX: 0000000000000004 RCX: ffff888086cb4c00
RDX: 0000000000000002 RSI: 0000000000000004 RDI: ffff8880997f9920
RBP: ffff88808bffeec8 R08: ffff888086cb4380 R09: 0000000000000001
R10: 0000000000000000 R11: ffff888086cb4380 R12: 0000000000000000
R13: ffff888080bfd500 R14: 0000000000000010 R15: ffff88808098b540
FS: 00007f391fdbc700(0000) GS:ffff8880aec00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f66ae47d9b8 CR3: 000000009350a000 CR4: 00000000001406f0
RSP: 002b:00007f391fdbbdb8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00000000006dbc88 RCX: 0000000000446d89
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000009
RBP: 00000000006dbc80 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000000246 R12: 00000000006dbc8c
R13: 00007ffc0185f22f R14: 00007f391fdbc9c0 R15: 20c49ba5e353f7cf
Code: 10 e8 47 84 fb fa 4c 89 e7 be 04 00 00 00 e8 4a ac ff ff 4c 8d 70 10
49 89 c4 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00
0f 85 0d 05 00 00 48 b8 00 00 00 00 00 fc ff df 49
RIP: hsr_check_carrier_and_operstate+0x3e/0x5e0 net/hsr/hsr_device.c:116
RSP: ffff88808bffee90
49 89 c4 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00
0f 85 0d 05 00 00 48 b8 00 00 00 00 00 fc ff df 49
RIP: hsr_check_carrier_and_operstate+0x3e/0x5e0 net/hsr/hsr_device.c:116
---[ end trace 3a402e1c952e2ff2 ]---
syzbot
Jan 8, 2020, 8:05:11 PM1/8/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 3d40d711 Linux 4.19.93
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16f7a9e1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=be639726c8387103
dashboard link: https://syzkaller.appspot.com/bug?extid=7869c881689986d95bf5
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1712cb25e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+7869c8...@syzkaller.appspotmail.com
device bridge33 entered promiscuous mode
device bridge32 entered promiscuous mode
net/hsr/hsr_device.c:116
Code: fa 4c 89 e7 be 04 00 00 00 e8 4a a4 ff ff 49 89 c4 48 83 c0 10 48 89
c2 48 89 45 d0 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f
85 da 05 00 00 48 b8 00 00 00 00 00 fc ff df 49 8b
RSP: 0018:ffff88809f206bb8 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000004 RCX: ffffffff874ae805
RDX: 0000000000000002 RSI: ffffffff874ae80f RDI: 0000000000000004
RBP: ffff88809f206bf8 R08: ffff88807e0bc600 R09: fffffbfff134206d
R10: fffffbfff134206c R11: ffffffff89a10367 R12: 0000000000000000
R13: ffff88809ffa1d80 R14: dffffc0000000000 R15: 0000000000000000
FS: 00007f7255776700(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
notifier_call_chain+0xc2/0x230 kernel/notifier.c:93
netdev_state_change net/core/dev.c:1352 [inline]
netdev_state_change+0x10d/0x140 net/core/dev.c:1345
do_setlink+0x2c78/0x3670 net/core/rtnetlink.c:2661
rtnl_newlink+0xbad/0x1600 net/core/rtnetlink.c:3068
rtnetlink_rcv_msg+0x463/0xb00 net/core/rtnetlink.c:4768
netlink_rcv_skb+0x17d/0x460 net/netlink/af_netlink.c:2454
rtnetlink_rcv+0x1d/0x30 net/core/rtnetlink.c:4786
netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
netlink_unicast+0x53a/0x730 net/netlink/af_netlink.c:1343
netlink_sendmsg+0x8ae/0xd70 net/netlink/af_netlink.c:1908
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xd7/0x130 net/socket.c:632
___sys_sendmsg+0x803/0x920 net/socket.c:2115
__sys_sendmsg+0x105/0x1d0 net/socket.c:2153
__do_sys_sendmsg net/socket.c:2162 [inline]
__se_sys_sendmsg net/socket.c:2160 [inline]
__x64_sys_sendmsg+0x78/0xb0 net/socket.c:2160
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x446d89
Code: e8 5c b3 02 00 48 83 c4 18 c3 0f 1f 80 00 00 00 00 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 0b 08 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f7255775db8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00000000006dbc98 RCX: 0000000000446d89
R10: 0000000000000004 R11: 0000000000000246 R12: 00000000006dbc9c
R13: 00007fff224794bf R14: 00007f72557769c0 R15: 20c49ba5e353f7cf
Modules linked in:
---[ end trace 9c01e0bf656b717f ]---
RIP: 0010:hsr_check_carrier_and_operstate+0x42/0x6c0
net/hsr/hsr_device.c:116
Code: fa 4c 89 e7 be 04 00 00 00 e8 4a a4 ff ff 49 89 c4 48 83 c0 10 48 89
c2 48 89 45 d0 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f
85 da 05 00 00 48 b8 00 00 00 00 00 fc ff df 49 8b
RSP: 0018:ffff88809f206bb8 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000004 RCX: ffffffff874ae805
RDX: 0000000000000002 RSI: ffffffff874ae80f RDI: 0000000000000004
RBP: ffff88809f206bf8 R08: ffff88807e0bc600 R09: fffffbfff134206d
R10: fffffbfff134206c R11: ffffffff89a10367 R12: 0000000000000000
R13: ffff88809ffa1d80 R14: dffffc0000000000 R15: 0000000000000000
FS: 00007f7255776700(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
https://goo.gl/tpsmEJ#testing-patches
syzbot found the following crash on:
HEAD commit: 3d40d711 Linux 4.19.93
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16f7a9e1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=be639726c8387103
dashboard link: https://syzkaller.appspot.com/bug?extid=7869c881689986d95bf5
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10dfc3fee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1712cb25e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
device bridge33 entered promiscuous mode
device bridge32 entered promiscuous mode
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: 8747 Comm: syz-executor427 Not tainted 4.19.93-syzkaller #0
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:hsr_check_carrier_and_operstate+0x42/0x6c0
Google 01/01/2011
net/hsr/hsr_device.c:116
Code: fa 4c 89 e7 be 04 00 00 00 e8 4a a4 ff ff 49 89 c4 48 83 c0 10 48 89
c2 48 89 45 d0 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f
85 da 05 00 00 48 b8 00 00 00 00 00 fc ff df 49 8b
RSP: 0018:ffff88809f206bb8 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000004 RCX: ffffffff874ae805
RDX: 0000000000000002 RSI: ffffffff874ae80f RDI: 0000000000000004
RBP: ffff88809f206bf8 R08: ffff88807e0bc600 R09: fffffbfff134206d
R10: fffffbfff134206c R11: ffffffff89a10367 R12: 0000000000000000
R13: ffff88809ffa1d80 R14: dffffc0000000000 R15: 0000000000000000
FS: 00007f7255776700(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f89776a63e0 CR3: 000000008ec97000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
hsr_netdev_notify+0x12a/0xa40 net/hsr/hsr_main.c:51
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
notifier_call_chain+0xc2/0x230 kernel/notifier.c:93
__raw_notifier_call_chain kernel/notifier.c:394 [inline]
raw_notifier_call_chain+0x2e/0x40 kernel/notifier.c:401
call_netdevice_notifiers_info+0x3f/0x90 net/core/dev.c:1747
raw_notifier_call_chain+0x2e/0x40 kernel/notifier.c:401
netdev_state_change net/core/dev.c:1352 [inline]
netdev_state_change+0x10d/0x140 net/core/dev.c:1345
do_setlink+0x2c78/0x3670 net/core/rtnetlink.c:2661
rtnl_newlink+0xbad/0x1600 net/core/rtnetlink.c:3068
rtnetlink_rcv_msg+0x463/0xb00 net/core/rtnetlink.c:4768
netlink_rcv_skb+0x17d/0x460 net/netlink/af_netlink.c:2454
rtnetlink_rcv+0x1d/0x30 net/core/rtnetlink.c:4786
netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
netlink_unicast+0x53a/0x730 net/netlink/af_netlink.c:1343
netlink_sendmsg+0x8ae/0xd70 net/netlink/af_netlink.c:1908
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xd7/0x130 net/socket.c:632
___sys_sendmsg+0x803/0x920 net/socket.c:2115
__sys_sendmsg+0x105/0x1d0 net/socket.c:2153
__do_sys_sendmsg net/socket.c:2162 [inline]
__se_sys_sendmsg net/socket.c:2160 [inline]
__x64_sys_sendmsg+0x78/0xb0 net/socket.c:2160
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x446d89
Code: e8 5c b3 02 00 48 83 c4 18 c3 0f 1f 80 00 00 00 00 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 0b 08 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f7255775db8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00000000006dbc98 RCX: 0000000000446d89
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000009
RBP: 00000000006dbc90 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000000246 R12: 00000000006dbc9c
R13: 00007fff224794bf R14: 00007f72557769c0 R15: 20c49ba5e353f7cf
Modules linked in:
---[ end trace 9c01e0bf656b717f ]---
RIP: 0010:hsr_check_carrier_and_operstate+0x42/0x6c0
net/hsr/hsr_device.c:116
Code: fa 4c 89 e7 be 04 00 00 00 e8 4a a4 ff ff 49 89 c4 48 83 c0 10 48 89
c2 48 89 45 d0 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f
85 da 05 00 00 48 b8 00 00 00 00 00 fc ff df 49 8b
RSP: 0018:ffff88809f206bb8 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000004 RCX: ffffffff874ae805
RDX: 0000000000000002 RSI: ffffffff874ae80f RDI: 0000000000000004
RBP: ffff88809f206bf8 R08: ffff88807e0bc600 R09: fffffbfff134206d
R10: fffffbfff134206c R11: ffffffff89a10367 R12: 0000000000000000
R13: ffff88809ffa1d80 R14: dffffc0000000000 R15: 0000000000000000
FS: 00007f7255776700(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007faa73d2d9b8 CR3: 000000008ec97000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
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 syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
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 syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages