[moderation] [serial?] KCSAN: data-race in __stop_tty / pty_write_room (11)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d1d36025a617 Merge tag 'probes-v6.19' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1596821a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=fe265072cbd2f67a
dashboard link: https://syzkaller.appspot.com/bug?extid=7740ee727a980f66bb9a
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
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/a49a20ff0279/disk-d1d36025.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/82299341ac86/vmlinux-d1d36025.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c7a8896df36f/bzImage-d1d36025.xz

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

==================================================================
BUG: KCSAN: data-race in __stop_tty / pty_write_room

write to 0xffff888111bccdbc of 1 bytes by task 4368 on cpu 1:
__stop_tty+0x36/0x90 drivers/tty/tty_io.c:744
n_tty_ioctl_helper+0x1e9/0x210 drivers/tty/tty_ioctl.c:951
n_tty_ioctl+0x101/0x200 drivers/tty/n_tty.c:2509
tty_ioctl+0x83f/0xb80 drivers/tty/tty_io.c:2801
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xce/0x140 fs/ioctl.c:583
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:583
x64_sys_call+0x14b0/0x3000 arch/x86/include/generated/asm/syscalls_64.h:17
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd8/0x2a0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888111bccdbc of 1 bytes by task 42 on cpu 0:
pty_write_room+0x19/0x70 drivers/tty/pty.c:131
tty_write_room+0x3f/0x60 drivers/tty/tty_ioctl.c:69
__process_echoes+0x36/0x6b0 drivers/tty/n_tty.c:687
flush_echoes drivers/tty/n_tty.c:791 [inline]
__receive_buf drivers/tty/n_tty.c:1626 [inline]
n_tty_receive_buf_common+0x8e4/0xbe0 drivers/tty/n_tty.c:1723
n_tty_receive_buf2+0x33/0x40 drivers/tty/n_tty.c:1769
tty_ldisc_receive_buf+0x66/0xf0 drivers/tty/tty_buffer.c:387
tty_port_default_receive_buf+0x59/0x90 drivers/tty/tty_port.c:37
receive_buf drivers/tty/tty_buffer.c:445 [inline]
flush_to_ldisc+0x148/0x340 drivers/tty/tty_buffer.c:495
process_one_work kernel/workqueue.c:3257 [inline]
process_scheduled_works+0x4ce/0x9d0 kernel/workqueue.c:3340
worker_thread+0x582/0x770 kernel/workqueue.c:3421
kthread+0x489/0x510 kernel/kthread.c:463
ret_from_fork+0x149/0x290 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246

value changed: 0x00 -> 0x01

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 42 Comm: kworker/u8:2 Not tainted syzkaller #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: events_unbound flush_to_ldisc
==================================================================


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