[moderation] [kernel?] KCSAN: data-race in pcpu_alloc / pcpu_balance_workfn (9)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 52b1853b080a Merge tag 'i2c-for-6.7-final' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1743d1ade80000
kernel config: https://syzkaller.appspot.com/x/.config?x=17e138c8fc533c5e
dashboard link: https://syzkaller.appspot.com/bug?extid=7edf073787e0af52dd06
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [b...@alien8.de dave....@linux.intel.com h...@zytor.com linux-...@vger.kernel.org mi...@redhat.com tg...@linutronix.de x...@kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/32436e2e6cf1/disk-52b1853b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c0a27bdf8e03/vmlinux-52b1853b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f165b88f9643/bzImage-52b1853b.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7edf07...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in pcpu_alloc / pcpu_balance_workfn

read-write to 0xffffffff86ef831c of 4 bytes by task 3191 on cpu 1:
pcpu_update_empty_pages mm/percpu.c:602 [inline]
pcpu_chunk_populated mm/percpu.c:1531 [inline]
pcpu_balance_populated mm/percpu.c:2088 [inline]
pcpu_balance_workfn+0x94c/0xa50 mm/percpu.c:2238
process_one_work kernel/workqueue.c:2627 [inline]
process_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2700
worker_thread+0x525/0x730 kernel/workqueue.c:2781
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

read to 0xffffffff86ef831c of 4 bytes by task 13806 on cpu 0:
pcpu_alloc+0x9bc/0x10b0 mm/percpu.c:1868
__alloc_percpu_gfp+0x26/0x30 mm/percpu.c:1930
bpf_map_alloc_percpu+0xaa/0x200 kernel/bpf/syscall.c:467
prealloc_init+0x19f/0x470 kernel/bpf/hashtab.c:337
htab_map_alloc+0x715/0x9e0 kernel/bpf/hashtab.c:568
map_create+0x713/0xa40 kernel/bpf/syscall.c:1210
__sys_bpf+0x62a/0x780 kernel/bpf/syscall.c:5365
__do_sys_bpf kernel/bpf/syscall.c:5487 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5485 [inline]
__x64_sys_bpf+0x43/0x50 kernel/bpf/syscall.c:5485
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00000001 -> 0x00000004

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 13806 Comm: syz-executor.2 Tainted: G W 6.7.0-rc8-syzkaller-00177-g52b1853b080a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
==================================================================


---
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 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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.