syzbot


KCSAN: data-race in __stop_tty / pty_write (12)

Status: auto-obsoleted due to no activity on 2024/03/18 19:09
Subsystems: serial
[Documentation on labels]
Reported-by: syzbot+75bffff65389d96c5264@syzkaller.appspotmail.com
First crash: 157d, last: 95d
Similar bugs (12)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in __stop_tty / pty_write serial 1 1037d 1037d 0/26 auto-closed as invalid on 2021/08/19 13:20
upstream KCSAN: data-race in __stop_tty / pty_write (6) serial 1 730d 730d 0/26 auto-closed as invalid on 2022/06/22 11:40
upstream KCSAN: data-race in __stop_tty / pty_write (8) serial 4 391d 406d 0/26 auto-obsoleted due to no activity on 2023/05/28 07:29
upstream KCSAN: data-race in __stop_tty / pty_write (9) serial 3 300d 331d 0/26 auto-obsoleted due to no activity on 2023/08/26 21:27
upstream KCSAN: data-race in __stop_tty / pty_write (2) serial 1 955d 955d 0/26 auto-closed as invalid on 2021/11/09 20:04
upstream KCSAN: data-race in __stop_tty / pty_write (4) serial 1 827d 827d 0/26 auto-closed as invalid on 2022/03/17 12:14
upstream KCSAN: data-race in __stop_tty / pty_write (3) serial 1 915d 915d 0/26 auto-closed as invalid on 2021/12/20 07:00
upstream KCSAN: data-race in __stop_tty / pty_write (13) serial 10 3d09h 59d 0/26 moderation: reported on 2024/03/20 09:24
upstream KCSAN: data-race in __stop_tty / pty_write (5) serial 1 784d 784d 0/26 auto-closed as invalid on 2022/04/30 10:57
upstream KCSAN: data-race in __stop_tty / pty_write (10) serial 1 252d 252d 0/26 auto-obsoleted due to no activity on 2023/10/14 11:29
upstream KCSAN: data-race in __stop_tty / pty_write (11) serial 3 208d 211d 0/26 auto-obsoleted due to no activity on 2023/11/26 18:07
upstream KCSAN: data-race in __stop_tty / pty_write (7) serial 1 589d 589d 0/26 auto-obsoleted due to no activity on 2022/11/10 14:49

Sample crash report:
==================================================================
BUG: KCSAN: data-race in __stop_tty / pty_write

write to 0xffff88814480fdbc of 1 bytes by task 11653 on cpu 0:
 __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+0xcd/0x1d0 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff88814480fdbc of 1 bytes by task 8705 on cpu 1:
 pty_write+0x26/0xa0 drivers/tty/pty.c:115
 tty_put_char+0x83/0xb0 drivers/tty/tty_io.c:3168
 n_tty_process_echo_ops drivers/tty/n_tty.c:664 [inline]
 __process_echoes+0x3a3/0x6a0 drivers/tty/n_tty.c:709
 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/0xa40 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: 1 PID: 8705 Comm: kworker/u4:9 Not tainted 6.8.0-rc4-syzkaller-00003-g716f4aaa7b48 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: events_unbound flush_to_ldisc
==================================================================

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/12 19:08 upstream 716f4aaa7b48 77b23aa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in __stop_tty / pty_write
2024/02/08 23:44 upstream 047371968ffc 7f07e9b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in __stop_tty / pty_write
2024/02/08 14:02 upstream 047371968ffc 6404acf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in __stop_tty / pty_write
2024/01/11 06:49 upstream de927f6c0b07 00f3cc59 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in __stop_tty / pty_write
2024/01/10 23:27 upstream ab27740f7665 04815ef1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in __stop_tty / pty_write
2023/12/22 15:59 upstream 24e0d2e527a3 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in __stop_tty / pty_write
2023/12/13 11:16 upstream 88035e5694a8 ebcad15c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in __stop_tty / pty_write
* Struck through repros no longer work on HEAD.