syzbot


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

Status: auto-closed as invalid on 2022/04/30 10:57
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 256d, last: 256d
similar bugs (6):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in __stop_tty / pty_write 1 510d 510d 0/24 auto-closed as invalid on 2021/08/19 13:20
upstream KCSAN: data-race in __stop_tty / pty_write (6) 1 203d 203d 0/24 auto-closed as invalid on 2022/06/22 11:40
upstream KCSAN: data-race in __stop_tty / pty_write (2) 1 428d 428d 0/24 auto-closed as invalid on 2021/11/09 20:04
upstream KCSAN: data-race in __stop_tty / pty_write (4) 1 300d 300d 0/24 auto-closed as invalid on 2022/03/17 12:14
upstream KCSAN: data-race in __stop_tty / pty_write (3) 1 387d 387d 0/24 auto-closed as invalid on 2021/12/20 07:00
upstream KCSAN: data-race in __stop_tty / pty_write (7) 1 62d 62d 0/24 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 0xffff888138eb1dbc of 1 bytes by task 16061 on cpu 0:
 __stop_tty+0x3e/0x80 drivers/tty/tty_io.c:760
 n_tty_ioctl_helper+0x310/0x450 drivers/tty/tty_ioctl.c:872
 n_tty_ioctl+0xfc/0x1f0 drivers/tty/n_tty.c:2381
 tty_ioctl+0xaf7/0x1130 drivers/tty/tty_io.c:2787
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl+0xcb/0x140 fs/ioctl.c:856
 __x64_sys_ioctl+0x3f/0x50 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888138eb1dbc of 1 bytes by task 43 on cpu 1:
 pty_write+0x38/0x120 drivers/tty/pty.c:116
 tty_put_char+0x7f/0xa0 drivers/tty/tty_io.c:3144
 __process_echoes+0x3ad/0x660 drivers/tty/n_tty.c:711
 flush_echoes drivers/tty/n_tty.c:812 [inline]
 __receive_buf drivers/tty/n_tty.c:1551 [inline]
 n_tty_receive_buf_common+0x4c38/0x4e70 drivers/tty/n_tty.c:1645
 n_tty_receive_buf2+0x2e/0x40 drivers/tty/n_tty.c:1680
 tty_ldisc_receive_buf+0x5b/0xf0 drivers/tty/tty_buffer.c:451
 tty_port_default_receive_buf+0x54/0x80 drivers/tty/tty_port.c:39
 receive_buf drivers/tty/tty_buffer.c:471 [inline]
 flush_to_ldisc+0x1c5/0x300 drivers/tty/tty_buffer.c:521
 process_one_work+0x3e3/0x970 kernel/workqueue.c:2289
 worker_thread+0x638/0xaa0 kernel/workqueue.c:2436
 kthread+0x1bf/0x1e0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30

value changed: 0x00 -> 0x01

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 43 Comm: kworker/u4:2 Not tainted 5.17.0-syzkaller-10752-g52d543b5497c-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_unbound flush_to_ldisc
==================================================================

Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-upstream-kcsan-gce 2022/03/26 10:56 upstream 52d543b5497c 89bc8608 .config log report info KCSAN: data-race in __stop_tty / pty_write
* Struck through repros no longer work on HEAD.