From: syzbot <syzbot+df838a721c117d596976@syzkaller.appspotmail.com>
To: acme@kernel.org, alexander.shishkin@linux.intel.com,
andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com, jolsa@redhat.com,
kafai@fb.com, kpsingh@kernel.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, mark.rutland@arm.com,
mingo@redhat.com, namhyung@kernel.org, netdev@vger.kernel.org,
peterz@infradead.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com
Subject: [syzbot] KCSAN: data-race in perf_event_update_userpage / perf_event_update_userpage (5)
Date: Thu, 10 Feb 2022 02:09:28 -0800 [thread overview]
Message-ID: <000000000000489d6105d7a7255e@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: dcb85f85fa6f gcc-plugins/stackleak: Use noinstr in favor o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14f2e20c700000
kernel config: https://syzkaller.appspot.com/x/.config?x=a83209f215159f48
dashboard link: https://syzkaller.appspot.com/bug?extid=df838a721c117d596976
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
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+df838a721c117d596976@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in perf_event_update_userpage / perf_event_update_userpage
write to 0xffff88812430e020 of 8 bytes by task 11328 on cpu 1:
perf_event_update_userpage+0x328/0x3b0 kernel/events/core.c:5941
cpu_clock_event_add+0x11d/0x130 kernel/events/core.c:10780
event_sched_in+0x781/0xe60 kernel/events/core.c:2601
group_sched_in kernel/events/core.c:2637 [inline]
merge_sched_in kernel/events/core.c:3802 [inline]
visit_groups_merge+0x943/0x1a50 kernel/events/core.c:3746
ctx_flexible_sched_in kernel/events/core.c:3844 [inline]
ctx_sched_in+0x221/0x240 kernel/events/core.c:3892
perf_event_sched_in kernel/events/core.c:2741 [inline]
perf_event_context_sched_in kernel/events/core.c:3943 [inline]
__perf_event_task_sched_in+0x37c/0x8d0 kernel/events/core.c:3986
perf_event_task_sched_in include/linux/perf_event.h:1213 [inline]
finish_task_switch+0x1ef/0x280 kernel/sched/core.c:4861
context_switch kernel/sched/core.c:4989 [inline]
__schedule+0x43a/0x690 kernel/sched/core.c:6295
preempt_schedule_common kernel/sched/core.c:6461 [inline]
__cond_resched+0x3f/0x90 kernel/sched/core.c:8174
might_resched include/linux/kernel.h:110 [inline]
might_alloc include/linux/sched/mm.h:256 [inline]
slab_pre_alloc_hook mm/slab.h:705 [inline]
slab_alloc mm/slab.c:3298 [inline]
kmem_cache_alloc+0x45/0x320 mm/slab.c:3499
kmem_cache_zalloc include/linux/slab.h:705 [inline]
__proc_create+0x3cf/0x6a0 fs/proc/generic.c:426
_proc_mkdir+0x5c/0xf0 fs/proc/generic.c:487
proc_net_mkdir include/linux/proc_fs.h:226 [inline]
nfs_fs_proc_net_init+0x79/0x140 fs/nfs/client.c:1329
nfs_net_init+0x19/0x20 fs/nfs/inode.c:2346
ops_init+0x1e7/0x230 net/core/net_namespace.c:140
setup_net+0x29b/0x7e0 net/core/net_namespace.c:330
copy_net_ns+0x2a9/0x450 net/core/net_namespace.c:474
create_new_namespaces+0x231/0x560 kernel/nsproxy.c:110
copy_namespaces+0x116/0x160 kernel/nsproxy.c:178
copy_process+0x1428/0x2f30 kernel/fork.c:2167
kernel_clone+0x15c/0x6a0 kernel/fork.c:2555
__do_sys_clone kernel/fork.c:2672 [inline]
__se_sys_clone kernel/fork.c:2656 [inline]
__x64_sys_clone+0xc6/0xf0 kernel/fork.c:2656
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
write to 0xffff88812430e020 of 8 bytes by task 11341 on cpu 0:
perf_event_update_userpage+0x328/0x3b0 kernel/events/core.c:5941
perf_mmap+0xcd6/0xe50 kernel/events/core.c:6419
call_mmap include/linux/fs.h:2079 [inline]
mmap_region+0xb04/0x10b0 mm/mmap.c:1793
do_mmap+0x781/0xc20 mm/mmap.c:1582
vm_mmap_pgoff+0x117/0x1f0 mm/util.c:519
ksys_mmap_pgoff+0x265/0x320 mm/mmap.c:1630
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
value changed: 0x0000000000000000 -> 0x000000000135f629
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 11341 Comm: syz-executor.4 Not tainted 5.17.0-rc2-syzkaller-00167-gdcb85f85fa6f-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================
---
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.
reply other threads:[~2022-02-10 10:09 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=000000000000489d6105d7a7255e@google.com \
--to=syzbot+df838a721c117d596976@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--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=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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).