[moderation] [mm?] KCSAN: data-race in __anon_vma_prepare / handle_mm_fault (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 23acd177540d Merge tag 'vfs-6.13.ecryptfs' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16b15ac0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=44f4147e19698730
dashboard link: https://syzkaller.appspot.com/bug?extid=94703445c693653e6d44
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a063bc39960c/disk-23acd177.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/47727532d600/vmlinux-23acd177.xz
kernel image: https://storage.googleapis.com/syzbot-assets/99056cf62ce2/bzImage-23acd177.xz

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

==================================================================
BUG: KCSAN: data-race in __anon_vma_prepare / handle_mm_fault

write to 0xffff888115ef7748 of 8 bytes by task 15774 on cpu 1:
__anon_vma_prepare+0x180/0x310 mm/rmap.c:214
__vmf_anon_prepare mm/memory.c:3307 [inline]
vmf_anon_prepare mm/internal.h:371 [inline]
do_anonymous_page mm/memory.c:4780 [inline]
do_pte_missing mm/memory.c:3963 [inline]
handle_pte_fault mm/memory.c:5766 [inline]
__handle_mm_fault mm/memory.c:5909 [inline]
handle_mm_fault+0x1c5d/0x2aa0 mm/memory.c:6077
do_user_addr_fault arch/x86/mm/fault.c:1389 [inline]
handle_page_fault arch/x86/mm/fault.c:1481 [inline]
exc_page_fault+0x296/0x650 arch/x86/mm/fault.c:1539
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
rep_movs_alternative+0x33/0x70 arch/x86/lib/copy_user_64.S:57
copy_user_generic arch/x86/include/asm/uaccess_64.h:126 [inline]
raw_copy_to_user arch/x86/include/asm/uaccess_64.h:147 [inline]
_inline_copy_to_user include/linux/uaccess.h:197 [inline]
_copy_to_user+0x7c/0xa0 lib/usercopy.c:26
copy_to_user include/linux/uaccess.h:225 [inline]
put_timespec64+0x64/0xb0 kernel/time/time.c:910
__do_sys_clock_getres kernel/time/posix-timers.c:1279 [inline]
__se_sys_clock_getres kernel/time/posix-timers.c:1267 [inline]
__x64_sys_clock_getres+0x143/0x190 kernel/time/posix-timers.c:1267
x64_sys_call+0x12a5/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:230
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888115ef7748 of 8 bytes by task 15773 on cpu 0:
__vmf_anon_prepare mm/memory.c:3301 [inline]
vmf_anon_prepare mm/internal.h:371 [inline]
do_anonymous_page mm/memory.c:4780 [inline]
do_pte_missing mm/memory.c:3963 [inline]
handle_pte_fault mm/memory.c:5766 [inline]
__handle_mm_fault mm/memory.c:5909 [inline]
handle_mm_fault+0xd87/0x2aa0 mm/memory.c:6077
do_user_addr_fault arch/x86/mm/fault.c:1338 [inline]
handle_page_fault arch/x86/mm/fault.c:1481 [inline]
exc_page_fault+0x3b9/0x650 arch/x86/mm/fault.c:1539
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623

value changed: 0x0000000000000000 -> 0xffff888114d60138

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 15773 Comm: syz.0.4489 Not tainted 6.12.0-syzkaller-00171-g23acd177540d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/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 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.