[moderation] [serial?] KCSAN: data-race in ppp_asynctty_receive / tty_set_termios (9)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2d5404caa8c7 Linux 6.12-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11f3935f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=29fedde79f609854
dashboard link: https://syzkaller.appspot.com/bug?extid=f54ea0eff13980f84a22
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/15a7713979b8/disk-2d5404ca.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b51c4f695d4a/vmlinux-2d5404ca.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e8c0f17bc00b/bzImage-2d5404ca.xz

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

BUG: KCSAN: data-race in ppp_asynctty_receive / tty_set_termios

read-write to 0xffff888112bac908 of 4 bytes by task 11591 on cpu 0:
unset_locked_termios drivers/tty/tty_ioctl.c:214 [inline]
tty_set_termios+0xfa/0x8b0 drivers/tty/tty_ioctl.c:340
set_termios+0x497/0x4e0 drivers/tty/tty_ioctl.c:516
tty_mode_ioctl+0x391/0x5d0
read to 0xffff888112bac908 of 4 bytes by task 1653 on cpu 1:
worker_thread+0x51d/0x6f0 kernel/workqueue.c:3391
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
Reported by Kernel Concurrency Sanitizer on:


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