[moderation] [serial?] KCSAN: data-race in n_tty_write / tty_set_termios (13)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 89be9a83ccf1 Linux 6.16-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11ebafd4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c0dd0a92e88efc24
dashboard link: https://syzkaller.appspot.com/bug?extid=78b30a49576e06e0809b
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
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/0ddf56b16465/disk-89be9a83.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d352fc68f5dd/vmlinux-89be9a83.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2cfbbbe4e4f4/bzImage-89be9a83.xz

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

==================================================================
BUG: KCSAN: data-race in n_tty_write / tty_set_termios

write to 0xffff888118f62508 of 44 bytes by task 14225 on cpu 1:
tty_set_termios+0xc0/0x8c0 drivers/tty/tty_ioctl.c:335
set_termios+0x35b/0x4e0 drivers/tty/tty_ioctl.c:516
tty_mode_ioctl+0x379/0x5c0 drivers/tty/tty_ioctl.c:-1
n_tty_ioctl_helper+0x91/0x210 drivers/tty/tty_ioctl.c:982
n_tty_ioctl+0x101/0x200 drivers/tty/n_tty.c:2509
tty_ioctl+0x845/0xb80 drivers/tty/tty_io.c:2801
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:907 [inline]
__se_sys_ioctl+0xcb/0x140 fs/ioctl.c:893
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:893
x64_sys_call+0x19a8/0x2fb0 arch/x86/include/generated/asm/syscalls_64.h:17
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd2/0x200 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888118f62514 of 4 bytes by task 14212 on cpu 0:
n_tty_write+0x9f/0xb10 drivers/tty/n_tty.c:2354
iterate_tty_write drivers/tty/tty_io.c:1006 [inline]
file_tty_write+0x38c/0x670 drivers/tty/tty_io.c:1081
tty_write+0x25/0x30 drivers/tty/tty_io.c:1102
new_sync_write fs/read_write.c:593 [inline]
vfs_write+0x49d/0x8e0 fs/read_write.c:686
ksys_write+0xda/0x1a0 fs/read_write.c:738
__do_sys_write fs/read_write.c:749 [inline]
__se_sys_write fs/read_write.c:746 [inline]
__x64_sys_write+0x40/0x50 fs/read_write.c:746
x64_sys_call+0x2cdd/0x2fb0 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd2/0x200 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00008a3b -> 0x00000760

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 14212 Comm: syz.1.3855 Not tainted 6.16.0-rc7-syzkaller #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
==================================================================


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