WARNING in tracepoint_add_func (2)
9 views
Skip to first unread message
syzbot
Feb 14, 2021, 2:49:15 PM2/14/21
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 2c8a3fce Linux 4.14.218
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12249914d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=80e596b8b0902d96
dashboard link: https://syzkaller.appspot.com/bug?extid=067e4e5eefed7bd9a6dd
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+067e4e...@syzkaller.appspotmail.com
bridge0: port 1(bridge_slave_0) entered forwarding state
device bridge0 left promiscuous mode
bridge0: port 2(bridge_slave_1) entered disabled state
------------[ cut here ]------------
bridge0: port 1(bridge_slave_0) entered disabled state
WARNING: CPU: 1 PID: 11905 at kernel/tracepoint.c:210 tracepoint_add_func+0x21a/0x750 syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:210
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 11905 Comm: syz-executor.2 Not tainted 4.14.218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:58
panic+0x1f9/0x42d syzkaller/managers/linux-4-14/kernel/kernel/panic.c:183
__warn.cold+0x20/0x44 syzkaller/managers/linux-4-14/kernel/kernel/panic.c:547
report_bug+0x208/0x250 syzkaller/managers/linux-4-14/kernel/lib/bug.c:186
fixup_bug syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/traps.c:177 [inline]
fixup_bug syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/entry_64.S:964
RIP: 0010:tracepoint_add_func+0x21a/0x750 syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:210
RSP: 0018:ffff8880494d7b48 EFLAGS: 00010216
RAX: 0000000000040000 RBX: ffffffff88f570c0 RCX: ffffc90008d2a000
RDX: 0000000000001573 RSI: ffffffff815638ca RDI: ffff8880a2746930
RBP: ffffffff81387110 R08: 0000000000000000 R09: 0000000000040637
R10: ffff8880571e4f00 R11: ffff8880571e4600 R12: 00000000ffffffef
R13: 00000000ffffffff R14: ffff8880a2746910 R15: dffffc0000000000
tracepoint_probe_register_prio syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:283 [inline]
tracepoint_probe_register+0x8c/0xc0 syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:304
trace_event_reg+0x272/0x330 syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_events.c:305
perf_trace_event_reg syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:122 [inline]
perf_trace_event_init syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:197 [inline]
perf_trace_init+0x424/0xa30 syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:221
perf_tp_event_init+0x79/0xf0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:8138
perf_try_init_event+0x15b/0x1f0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9369
perf_init_event syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9407 [inline]
perf_event_alloc.part.0+0xe2d/0x2640 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9667
perf_event_alloc syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10020 [inline]
SYSC_perf_event_open syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10124 [inline]
SyS_perf_event_open+0x67f/0x24b0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10010
do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x465d99
RSP: 002b:00007efd42c6d188 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465d99
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000100
RBP: 00000000004bcf27 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 000000000056bf60
R13: 00007ffc25d07f3f R14: 00007efd42c6d300 R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following issue on:
HEAD commit: 2c8a3fce Linux 4.14.218
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12249914d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=80e596b8b0902d96
dashboard link: https://syzkaller.appspot.com/bug?extid=067e4e5eefed7bd9a6dd
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+067e4e...@syzkaller.appspotmail.com
bridge0: port 1(bridge_slave_0) entered forwarding state
device bridge0 left promiscuous mode
bridge0: port 2(bridge_slave_1) entered disabled state
------------[ cut here ]------------
bridge0: port 1(bridge_slave_0) entered disabled state
WARNING: CPU: 1 PID: 11905 at kernel/tracepoint.c:210 tracepoint_add_func+0x21a/0x750 syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:210
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 11905 Comm: syz-executor.2 Not tainted 4.14.218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:58
panic+0x1f9/0x42d syzkaller/managers/linux-4-14/kernel/kernel/panic.c:183
__warn.cold+0x20/0x44 syzkaller/managers/linux-4-14/kernel/kernel/panic.c:547
report_bug+0x208/0x250 syzkaller/managers/linux-4-14/kernel/lib/bug.c:186
fixup_bug syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/traps.c:177 [inline]
fixup_bug syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/entry_64.S:964
RIP: 0010:tracepoint_add_func+0x21a/0x750 syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:210
RSP: 0018:ffff8880494d7b48 EFLAGS: 00010216
RAX: 0000000000040000 RBX: ffffffff88f570c0 RCX: ffffc90008d2a000
RDX: 0000000000001573 RSI: ffffffff815638ca RDI: ffff8880a2746930
RBP: ffffffff81387110 R08: 0000000000000000 R09: 0000000000040637
R10: ffff8880571e4f00 R11: ffff8880571e4600 R12: 00000000ffffffef
R13: 00000000ffffffff R14: ffff8880a2746910 R15: dffffc0000000000
tracepoint_probe_register_prio syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:283 [inline]
tracepoint_probe_register+0x8c/0xc0 syzkaller/managers/linux-4-14/kernel/kernel/tracepoint.c:304
trace_event_reg+0x272/0x330 syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_events.c:305
perf_trace_event_reg syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:122 [inline]
perf_trace_event_init syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:197 [inline]
perf_trace_init+0x424/0xa30 syzkaller/managers/linux-4-14/kernel/kernel/trace/trace_event_perf.c:221
perf_tp_event_init+0x79/0xf0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:8138
perf_try_init_event+0x15b/0x1f0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9369
perf_init_event syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9407 [inline]
perf_event_alloc.part.0+0xe2d/0x2640 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:9667
perf_event_alloc syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10020 [inline]
SYSC_perf_event_open syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10124 [inline]
SyS_perf_event_open+0x67f/0x24b0 syzkaller/managers/linux-4-14/kernel/kernel/events/core.c:10010
do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x465d99
RSP: 002b:00007efd42c6d188 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465d99
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000100
RBP: 00000000004bcf27 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 000000000056bf60
R13: 00007ffc25d07f3f R14: 00007efd42c6d300 R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Feb 28, 2021, 11:00:16 AM2/28/21
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 3242aa3a Linux 4.14.222
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15929646d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d6fee509440d713f
dashboard link: https://syzkaller.appspot.com/bug?extid=067e4e5eefed7bd9a6dd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15db59ccd00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=109398ead00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+067e4e...@syzkaller.appspotmail.com
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000004
RBP: 00007ffd1055b140 R08: 0000000000000001 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000005
R13: 431bde82d7b634db R14: 00000000004ae018 R15: 00000000004004a0
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7971 at kernel/tracepoint.c:210 tracepoint_add_func+0x21a/0x750 kernel/tracepoint.c:210
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:tracepoint_add_func+0x21a/0x750 kernel/tracepoint.c:210
RSP: 0018:ffff8880a2acf658 EFLAGS: 00010297
RAX: ffff8880912f6200 RBX: 0000000000000000 RCX: 0000000000000001
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: ffff888096771518
RBP: ffffffff85cad7b0 R08: 0000000000000000 R09: 000000000004057e
R10: ffff8880912f6b00 R11: ffff8880912f6200 R12: 00000000ffffffef
R13: 00000000ffffffff R14: ffff888096771510 R15: dffffc0000000000
tracepoint_probe_register_prio kernel/tracepoint.c:283 [inline]
tracepoint_probe_register+0x8c/0xc0 kernel/tracepoint.c:304
register_trace_kfree_skb include/trace/events/skb.h:15 [inline]
set_all_monitor_traces net/core/drop_monitor.c:260 [inline]
net_dm_cmd_trace net/core/drop_monitor.c:311 [inline]
net_dm_cmd_trace+0x275/0x3a0 net/core/drop_monitor.c:306
genl_family_rcv_msg+0x572/0xb20 net/netlink/genetlink.c:600
genl_rcv_msg+0xaf/0x140 net/netlink/genetlink.c:625
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2433
genl_rcv+0x24/0x40 net/netlink/genetlink.c:636
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1313
netlink_sendmsg+0x62e/0xb80 net/netlink/af_netlink.c:1878
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x4409b9
RSP: 002b:00007ffd1055b128 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00000000004409b9
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000004
RBP: 00007ffd1055b140 R08: 0000000000000001 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000005
R13: 431bde82d7b634db R14: 00000000004ae018 R15: 00000000004004a0
HEAD commit: 3242aa3a Linux 4.14.222
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15929646d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d6fee509440d713f
dashboard link: https://syzkaller.appspot.com/bug?extid=067e4e5eefed7bd9a6dd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15db59ccd00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=109398ead00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+067e4e...@syzkaller.appspotmail.com
RBP: 00007ffd1055b140 R08: 0000000000000001 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000005
R13: 431bde82d7b634db R14: 00000000004ae018 R15: 00000000004004a0
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7971 at kernel/tracepoint.c:210 tracepoint_add_func+0x21a/0x750 kernel/tracepoint.c:210
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 7971 Comm: syz-executor118 Not tainted 4.14.222-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
Call Trace:
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:tracepoint_add_func+0x21a/0x750 kernel/tracepoint.c:210
RSP: 0018:ffff8880a2acf658 EFLAGS: 00010297
RAX: ffff8880912f6200 RBX: 0000000000000000 RCX: 0000000000000001
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: ffff888096771518
RBP: ffffffff85cad7b0 R08: 0000000000000000 R09: 000000000004057e
R10: ffff8880912f6b00 R11: ffff8880912f6200 R12: 00000000ffffffef
R13: 00000000ffffffff R14: ffff888096771510 R15: dffffc0000000000
tracepoint_probe_register_prio kernel/tracepoint.c:283 [inline]
tracepoint_probe_register+0x8c/0xc0 kernel/tracepoint.c:304
register_trace_kfree_skb include/trace/events/skb.h:15 [inline]
set_all_monitor_traces net/core/drop_monitor.c:260 [inline]
net_dm_cmd_trace net/core/drop_monitor.c:311 [inline]
net_dm_cmd_trace+0x275/0x3a0 net/core/drop_monitor.c:306
genl_family_rcv_msg+0x572/0xb20 net/netlink/genetlink.c:600
genl_rcv_msg+0xaf/0x140 net/netlink/genetlink.c:625
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2433
genl_rcv+0x24/0x40 net/netlink/genetlink.c:636
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1313
netlink_sendmsg+0x62e/0xb80 net/netlink/af_netlink.c:1878
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x4409b9
RSP: 002b:00007ffd1055b128 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00000000004409b9
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000004
RBP: 00007ffd1055b140 R08: 0000000000000001 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000005
R13: 431bde82d7b634db R14: 00000000004ae018 R15: 00000000004004a0
Reply all
Reply to author
Forward
0 new messages