[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <6743acf4.050a0220.1cc393.004d.GAE@google.com>
Date: Sun, 24 Nov 2024 14:47:16 -0800
From: syzbot <syzbot+16a19b06125a2963eaee@...kaller.appspotmail.com>
To: acme@...nel.org, adrian.hunter@...el.com,
alexander.shishkin@...ux.intel.com, irogers@...gle.com, jolsa@...nel.org,
kan.liang@...ux.intel.com, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
mark.rutland@....com, mhiramat@...nel.org, mingo@...hat.com,
namhyung@...nel.org, oleg@...hat.com, peterz@...radead.org,
syzkaller-bugs@...glegroups.com
Subject: [syzbot] [perf?] [trace?] KCSAN: assert: race in srcu_gp_start_if_needed
Hello,
syzbot found the following issue on:
HEAD commit: 42d9e8b7ccdd Merge tag 'powerpc-6.13-1' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10a00778580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3d7fd5be0e73b8b
dashboard link: https://syzkaller.appspot.com/bug?extid=16a19b06125a2963eaee
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ef231513adc7/disk-42d9e8b7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/54caaac5960b/vmlinux-42d9e8b7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/85b5a6566143/bzImage-42d9e8b7.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+16a19b06125a2963eaee@...kaller.appspotmail.com
==================================================================
BUG: KCSAN: assert: race in srcu_get_delay kernel/rcu/srcutree.c:658 [inline]
BUG: KCSAN: assert: race in srcu_funnel_gp_start kernel/rcu/srcutree.c:1089 [inline]
BUG: KCSAN: assert: race in srcu_gp_start_if_needed+0x808/0x9f0 kernel/rcu/srcutree.c:1339
race at unknown origin, with assert no writes to 0xffffffff8676ffc8 of 8 bytes by task 6285 on cpu 0:
srcu_get_delay kernel/rcu/srcutree.c:658 [inline]
srcu_funnel_gp_start kernel/rcu/srcutree.c:1089 [inline]
srcu_gp_start_if_needed+0x808/0x9f0 kernel/rcu/srcutree.c:1339
__call_srcu kernel/rcu/srcutree.c:1384 [inline]
__synchronize_srcu+0x114/0x150 kernel/rcu/srcutree.c:1432
synchronize_srcu+0x1ae/0x1d0
uprobe_unregister_sync+0x1a/0x20 kernel/events/uprobes.c:1328
__probe_event_disable kernel/trace/trace_uprobe.c:1138 [inline]
probe_event_disable+0x1f5/0x240 kernel/trace/trace_uprobe.c:1222
trace_uprobe_register+0xbb/0x3c0 kernel/trace/trace_uprobe.c:1512
perf_trace_event_unreg+0x6c/0x1a0 kernel/trace/trace_event_perf.c:162
perf_uprobe_destroy+0x6a/0xf0 kernel/trace/trace_event_perf.c:345
_free_event+0x7ca/0xa10 kernel/events/core.c:5357
put_event kernel/events/core.c:5454 [inline]
perf_event_release_kernel+0x61a/0x670 kernel/events/core.c:5579
perf_release+0x1f/0x30 kernel/events/core.c:5589
__fput+0x17a/0x6d0 fs/file_table.c:450
____fput+0x1c/0x30 fs/file_table.c:478
task_work_run+0x13a/0x1a0 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xa8/0x120 kernel/entry/common.c:218
do_syscall_64+0xd6/0x1c0 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
value changed: 0x0000000000000000 -> 0x0000000000000001
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 6285 Comm: syz.1.1056 Not tainted 6.12.0-syzkaller-08756-g42d9e8b7ccdd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
==================================================================
---
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 syzkaller@...glegroups.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 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
Powered by blists - more mailing lists