[v5.15] WARNING in perf_event_release_kernel
2 views
Skip to first unread message
syzbot
Dec 25, 2023, 8:48:23 AM12/25/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d93fa2c78854 Linux 5.15.145
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13fb371ae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=68cb856f08cf8214
dashboard link: https://syzkaller.appspot.com/bug?extid=732a0a87685f80d378b4
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1562b1cee80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15735776e80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b93d4851e328/disk-d93fa2c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8304bb885b1e/vmlinux-d93fa2c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee891eb52846/bzImage-d93fa2c7.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+732a0a...@syzkaller.appspotmail.com
------------[ cut here ]------------
unexpected event refcount: 2; ptr=ffff88801def8bd0
WARNING: CPU: 0 PID: 3506 at kernel/events/core.c:5167 free_event kernel/events/core.c:5165 [inline]
WARNING: CPU: 0 PID: 3506 at kernel/events/core.c:5167 perf_event_release_kernel+0x794/0x870 kernel/events/core.c:5332
Modules linked in:
CPU: 0 PID: 3506 Comm: syz-executor147 Not tainted 5.15.145-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:free_event kernel/events/core.c:5165 [inline]
RIP: 0010:perf_event_release_kernel+0x794/0x870 kernel/events/core.c:5332
Code: 00 fc ff df 80 3c 08 00 48 8b 5c 24 20 74 08 4c 89 e7 e8 af 4d 29 00 49 8b 34 24 48 c7 c7 40 b8 92 8a 4c 89 fa e8 8c 4d ab ff <0f> 0b eb 82 e8 13 98 df ff eb 05 e8 0c 98 df ff 4c 8b 7c 24 18 49
RSP: 0018:ffffc90002b37860 EFLAGS: 00010246
RAX: 33d9f1618d540e00 RBX: ffffc90002b378e0 RCX: ffff88807ac40000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90002b37958 R08: ffffffff81665aec R09: ffffed10173467a8
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801def8df8
R13: 1ffff11003bdf1d4 R14: dead000000000100 R15: ffff88801def8bd0
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555556736ca8 CR3: 0000000022a16000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
perf_release+0x37/0x40 kernel/events/core.c:5353
__fput+0x3bf/0x890 fs/file_table.c:280
task_work_run+0x129/0x1a0 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x6a3/0x2480 kernel/exit.c:872
do_group_exit+0x144/0x310 kernel/exit.c:994
get_signal+0xc66/0x14e0 kernel/signal.c:2889
arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:148 [inline]
exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:291
RIP: 0033:0x7f0f3d864bf9
Code: Unable to access opcode bytes at RIP 0x7f0f3d864bcf.
RSP: 002b:00007ffd8cb9c148 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f0f3d864bf9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000200
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
</TASK>
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: d93fa2c78854 Linux 5.15.145
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13fb371ae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=68cb856f08cf8214
dashboard link: https://syzkaller.appspot.com/bug?extid=732a0a87685f80d378b4
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1562b1cee80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15735776e80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b93d4851e328/disk-d93fa2c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8304bb885b1e/vmlinux-d93fa2c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee891eb52846/bzImage-d93fa2c7.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+732a0a...@syzkaller.appspotmail.com
------------[ cut here ]------------
unexpected event refcount: 2; ptr=ffff88801def8bd0
WARNING: CPU: 0 PID: 3506 at kernel/events/core.c:5167 free_event kernel/events/core.c:5165 [inline]
WARNING: CPU: 0 PID: 3506 at kernel/events/core.c:5167 perf_event_release_kernel+0x794/0x870 kernel/events/core.c:5332
Modules linked in:
CPU: 0 PID: 3506 Comm: syz-executor147 Not tainted 5.15.145-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:free_event kernel/events/core.c:5165 [inline]
RIP: 0010:perf_event_release_kernel+0x794/0x870 kernel/events/core.c:5332
Code: 00 fc ff df 80 3c 08 00 48 8b 5c 24 20 74 08 4c 89 e7 e8 af 4d 29 00 49 8b 34 24 48 c7 c7 40 b8 92 8a 4c 89 fa e8 8c 4d ab ff <0f> 0b eb 82 e8 13 98 df ff eb 05 e8 0c 98 df ff 4c 8b 7c 24 18 49
RSP: 0018:ffffc90002b37860 EFLAGS: 00010246
RAX: 33d9f1618d540e00 RBX: ffffc90002b378e0 RCX: ffff88807ac40000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90002b37958 R08: ffffffff81665aec R09: ffffed10173467a8
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801def8df8
R13: 1ffff11003bdf1d4 R14: dead000000000100 R15: ffff88801def8bd0
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555556736ca8 CR3: 0000000022a16000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
perf_release+0x37/0x40 kernel/events/core.c:5353
__fput+0x3bf/0x890 fs/file_table.c:280
task_work_run+0x129/0x1a0 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x6a3/0x2480 kernel/exit.c:872
do_group_exit+0x144/0x310 kernel/exit.c:994
get_signal+0xc66/0x14e0 kernel/signal.c:2889
arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:148 [inline]
exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:291
RIP: 0033:0x7f0f3d864bf9
Code: Unable to access opcode bytes at RIP 0x7f0f3d864bcf.
RSP: 002b:00007ffd8cb9c148 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f0f3d864bf9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000200
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
</TASK>
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Dec 25, 2023, 8:49:23 AM12/25/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 4aa6747d9352 Linux 6.1.69
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13fc6ec9e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1e9066810307299
dashboard link: https://syzkaller.appspot.com/bug?extid=48ab933dba3b0b97b66f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17aa5231e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=105e48d9e80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/90e712af4aa7/disk-4aa6747d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bdaad5d91499/vmlinux-4aa6747d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/157abc0d55dc/bzImage-4aa6747d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
------------[ cut here ]------------
unexpected event refcount: 2; ptr=ffff888075a670d0
WARNING: CPU: 0 PID: 3562 at kernel/events/core.c:5073 free_event kernel/events/core.c:5071 [inline]
WARNING: CPU: 0 PID: 3562 at kernel/events/core.c:5073 perf_event_release_kernel+0x794/0x870 kernel/events/core.c:5238
Modules linked in:
CPU: 0 PID: 3562 Comm: syz-executor417 Not tainted 6.1.69-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:free_event kernel/events/core.c:5071 [inline]
RIP: 0010:perf_event_release_kernel+0x794/0x870 kernel/events/core.c:5238
Code: 00 fc ff df 80 3c 08 00 48 8b 5c 24 20 74 08 4c 89 e7 e8 0f 66 32 00 49 8b 34 24 48 c7 c7 00 9f f4 8a 4c 89 fa e8 1c f2 a2 ff <0f> 0b eb 82 e8 03 05 db ff eb 05 e8 fc 04 db ff 4c 8b 7c 24 18 49
RSP: 0018:ffffc9000395f700 EFLAGS: 00010246
RAX: 4ee83116101dbe00 RBX: ffffc9000395f780 RCX: ffff888076655940
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000395f7e8 R08: ffffffff81527dae R09: ffffed1017324f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888075a672f8
R13: 1ffff1100eb4ce74 R14: dead000000000100 R15: ffff888075a670d0
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200000cc CR3: 000000000ce8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
perf_release+0x37/0x40 kernel/events/core.c:5259
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__fput+0x3b7/0x890 fs/file_table.c:320
task_work_run+0x246/0x300 kernel/task_work.c:179
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xa73/0x26a0 kernel/exit.c:869
do_group_exit+0x202/0x2b0 kernel/exit.c:1019
get_signal+0x16f7/0x17d0 kernel/signal.c:2862
arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871
exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:168
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:299
RIP: 0033:0x7fc58bd74bf9
Code: Unable to access opcode bytes at 0x7fc58bd74bcf.
RSP: 002b:00007ffe35817968 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fc58bd74bf9
Reply all
Reply to author
Forward
0 new messages