[moderation] [serial?] KCSAN: data-race in n_tty_poll / n_tty_set_termios (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8a92980606e3 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12eab874980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c00b51a1d411353
dashboard link: https://syzkaller.appspot.com/bug?extid=a7e2f400e009149d531a
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/b0932ad98ab1/disk-8a929806.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/243f1993fb5f/vmlinux-8a929806.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8c13ddeac75d/bzImage-8a929806.xz

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

==================================================================
BUG: KCSAN: data-race in n_tty_poll / n_tty_set_termios

write to 0xffffc900001dd05d of 1 bytes by task 11196 on cpu 1:
n_tty_set_termios+0x1fd/0x850 drivers/tty/n_tty.c:1810
tty_set_termios+0x849/0x8b0 drivers/tty/tty_ioctl.c:352
set_termios+0x497/0x4e0 drivers/tty/tty_ioctl.c:516
tty_mode_ioctl+0x391/0x5d0
n_tty_ioctl_helper+0x8d/0x240 drivers/tty/tty_ioctl.c:986
n_tty_ioctl+0xfd/0x200 drivers/tty/n_tty.c:2511
tty_ioctl+0x886/0xbe0 drivers/tty/tty_io.c:2812
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:907 [inline]
__se_sys_ioctl+0xd3/0x150 fs/ioctl.c:893
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:893
x64_sys_call+0x1581/0x2d70 arch/x86/include/generated/asm/syscalls_64.h:17
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffffc900001dd05d of 1 bytes by task 11187 on cpu 0:
input_available_p drivers/tty/n_tty.c:1929 [inline]
n_tty_poll+0x27c/0x490 drivers/tty/n_tty.c:2458
tty_poll+0x7e/0x100 drivers/tty/tty_io.c:2214
vfs_poll include/linux/poll.h:84 [inline]
do_pollfd fs/select.c:873 [inline]
do_poll fs/select.c:921 [inline]
do_sys_poll+0x644/0xc10 fs/select.c:1016
__do_sys_ppoll fs/select.c:1122 [inline]
__se_sys_ppoll+0x1af/0x1f0 fs/select.c:1102
__x64_sys_ppoll+0x67/0x80 fs/select.c:1102
x64_sys_call+0xeaf/0x2d70 arch/x86/include/generated/asm/syscalls_64.h:272
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x10 -> 0x0c

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 11187 Comm: syz-executor.1 Tainted: G W 6.10.0-rc2-syzkaller-00235-g8a92980606e3 #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