[moderation] [mm?] KCSAN: data-race in do_madvise / do_madvise

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0450d2083be6 Merge tag '6.10-rc-smb-fix' of git://git.samb..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1347fd68980000
kernel config: https://syzkaller.appspot.com/x/.config?x=9cea9d6e22e152b5
dashboard link: https://syzkaller.appspot.com/bug?extid=cf5ad1c95534522a611b
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/04c015715988/disk-0450d208.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/93f908c0c5bd/vmlinux-0450d208.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ead896346b5c/bzImage-0450d208.xz

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

==================================================================
BUG: KCSAN: data-race in do_madvise / do_madvise

write to 0xffff888103220630 of 8 bytes by task 17120 on cpu 0:
update_hiwater_rss include/linux/mm.h:2657 [inline]
madvise_free_single_vma mm/madvise.c:781 [inline]
madvise_dontneed_free mm/madvise.c:899 [inline]
madvise_vma_behavior mm/madvise.c:1023 [inline]
madvise_walk_vmas mm/madvise.c:1248 [inline]
do_madvise+0x155c/0x2600 mm/madvise.c:1428
__do_sys_madvise mm/madvise.c:1441 [inline]
__se_sys_madvise mm/madvise.c:1439 [inline]
__x64_sys_madvise+0x61/0x70 mm/madvise.c:1439
x64_sys_call+0x2825/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:29
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888103220630 of 8 bytes by task 17119 on cpu 1:
update_hiwater_rss include/linux/mm.h:2656 [inline]
madvise_free_single_vma mm/madvise.c:781 [inline]
madvise_dontneed_free mm/madvise.c:899 [inline]
madvise_vma_behavior mm/madvise.c:1023 [inline]
madvise_walk_vmas mm/madvise.c:1248 [inline]
do_madvise+0x1534/0x2600 mm/madvise.c:1428
__do_sys_madvise mm/madvise.c:1441 [inline]
__se_sys_madvise mm/madvise.c:1439 [inline]
__x64_sys_madvise+0x61/0x70 mm/madvise.c:1439
x64_sys_call+0x2825/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:29
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x0000000000000850 -> 0x00000000000008f0

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 17119 Comm: syz-executor.4 Tainted: G W 6.9.0-syzkaller-08995-g0450d2083be6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/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.