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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7ed2632ec7d7 drm/ttm: fix ttm pool initialization for no-d..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13dc7c17e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bd33f45956bbc2
dashboard link: https://syzkaller.appspot.com/bug?extid=3fc1e4d220304d0b5ce9
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/ff6facc21dca/disk-7ed2632e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/be6ef58407dd/vmlinux-7ed2632e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f18ed26c2f87/bzImage-7ed2632e.xz

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

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

write to 0xffff88813b74e1bc of 1 bytes by task 4632 on cpu 1:
__stop_tty+0x42/0x90 drivers/tty/tty_io.c:753
n_tty_ioctl_helper+0x21f/0x240 drivers/tty/tty_ioctl.c:955
n_tty_ioctl+0xfd/0x200 drivers/tty/n_tty.c:2511
tty_ioctl+0x875/0xbc0 drivers/tty/tty_io.c:2812
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 0xffff88813b74e1bc of 1 bytes by task 23591 on cpu 0:
pty_write_room+0x1c/0x70 drivers/tty/pty.c:131
tty_write_room+0x38/0x50 drivers/tty/tty_ioctl.c:69
__process_echoes+0x36/0x6a0 drivers/tty/n_tty.c:703
flush_echoes drivers/tty/n_tty.c:807 [inline]
__receive_buf drivers/tty/n_tty.c:1632 [inline]
n_tty_receive_buf_common+0x8e6/0xbc0 drivers/tty/n_tty.c:1729
n_tty_receive_buf2+0x33/0x40 drivers/tty/n_tty.c:1775
tty_ldisc_receive_buf+0x60/0xe0 drivers/tty/tty_buffer.c:386
tty_port_default_receive_buf+0x59/0x90 drivers/tty/tty_port.c:37
receive_buf drivers/tty/tty_buffer.c:444 [inline]
flush_to_ldisc+0x1ca/0x400 drivers/tty/tty_buffer.c:494
process_one_work kernel/workqueue.c:2633 [inline]
process_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2706
worker_thread+0x525/0x730 kernel/workqueue.c:2787
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

value changed: 0x00 -> 0x01

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 23591 Comm: kworker/u4:54 Not tainted 6.8.0-rc1-syzkaller-00026-g7ed2632ec7d7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.