[moderation] [serial?] KCSAN: data-race in __se_sys_ioctl / __tty_hangup (5)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4fbbed787267 Merge tag 'timers-core-2024-01-21' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16e5cbdbe80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ba10a94c8ea40fe5
dashboard link: https://syzkaller.appspot.com/bug?extid=e9e338fda9dbcfec1167
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org jiri...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ae1396ce8757/disk-4fbbed78.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/779af4d1028c/vmlinux-4fbbed78.xz
kernel image: https://storage.googleapis.com/syzbot-assets/88804f956fb9/bzImage-4fbbed78.xz

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

==================================================================
BUG: KCSAN: data-race in __se_sys_ioctl / __tty_hangup

write to 0xffff88813231e0b0 of 8 bytes by task 30200 on cpu 0:
__tty_hangup+0x1e8/0x530 drivers/tty/tty_io.c:621
tty_vhangup drivers/tty/tty_io.c:700 [inline]
tty_ioctl+0x60a/0xbc0 drivers/tty/tty_io.c:2743
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xcf/0x140 fs/ioctl.c:857
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x59/0x120 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff88813231e0b0 of 8 bytes by task 30196 on cpu 1:
vfs_ioctl fs/ioctl.c:48 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xa6/0x140 fs/ioctl.c:857
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x59/0x120 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0xffffffff859c8e20 -> 0xffffffff85097340

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 30196 Comm: syz-executor.1 Tainted: G W 6.7.0-syzkaller-13004-g4fbbed787267 #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.