From: syzbot <syzbot+ef3b1bb7dd78b4e9109c@syzkaller.appspotmail.com>
To: acme@kernel.org, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, irogers@google.com,
jolsa@kernel.org, kan.liang@linux.intel.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
mark.rutland@arm.com, mingo@redhat.com, namhyung@kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [perf?] KCSAN: data-race in _free_event / perf_pending_task
Date: Wed, 31 Jul 2024 05:08:24 -0700 [thread overview]
Message-ID: <000000000000781a1e061e89f3be@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 94ede2a3e913 profiling: remove stale percpu flip buffer va..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1277094b980000
kernel config: https://syzkaller.appspot.com/x/.config?x=bc4a9b665a33d32c
dashboard link: https://syzkaller.appspot.com/bug?extid=ef3b1bb7dd78b4e9109c
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/44ee867c2428/disk-94ede2a3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/94d1e02bfdfd/vmlinux-94ede2a3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/954c62ebb0b0/bzImage-94ede2a3.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ef3b1bb7dd78b4e9109c@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in _free_event / perf_pending_task
write to 0xffff88812715a1e8 of 4 bytes by task 22781 on cpu 1:
perf_pending_task+0xe8/0x220 kernel/events/core.c:6869
task_work_run+0x13a/0x1a0 kernel/task_work.c:228
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:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xbe/0x130 kernel/entry/common.c:218
do_syscall_64+0xd6/0x1c0 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
read to 0xffff88812715a1e8 of 4 bytes by task 22780 on cpu 0:
perf_pending_task_sync kernel/events/core.c:5199 [inline]
_free_event+0x3d/0xa10 kernel/events/core.c:5223
put_event kernel/events/core.c:5351 [inline]
perf_event_release_kernel+0x61a/0x670 kernel/events/core.c:5476
perf_release+0x25/0x30 kernel/events/core.c:5486
__fput+0x192/0x6f0 fs/file_table.c:422
____fput+0x15/0x20 fs/file_table.c:450
task_work_run+0x13a/0x1a0 kernel/task_work.c:228
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:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xbe/0x130 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: 0x7ad5cf52 -> 0x00000000
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 22780 Comm: syz.3.5885 Not tainted 6.11.0-rc1-syzkaller-00043-g94ede2a3e913 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/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@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 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
reply other threads:[~2024-07-31 12:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000781a1e061e89f3be@google.com \
--to=syzbot+ef3b1bb7dd78b4e9109c@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).