syzbot


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

Status: auto-closed as invalid on 2022/03/17 12:14
Subsystems: serial
[Documentation on labels]
First crash: 863d, last: 863d
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 1073d 1073d 0/27 auto-closed as invalid on 2021/08/19 13:20
upstream KCSAN: data-race in __stop_tty / pty_write (6) serial 1 766d 766d 0/27 auto-closed as invalid on 2022/06/22 11:40
upstream KCSAN: data-race in __stop_tty / pty_write (8) serial 4 426d 442d 0/27 auto-obsoleted due to no activity on 2023/05/28 07:29
upstream KCSAN: data-race in __stop_tty / pty_write (9) serial 3 336d 367d 0/27 auto-obsoleted due to no activity on 2023/08/26 21:27
upstream KCSAN: data-race in __stop_tty / pty_write (2) serial 1 991d 991d 0/27 auto-closed as invalid on 2021/11/09 20:04
upstream KCSAN: data-race in __stop_tty / pty_write (3) serial 1 950d 950d 0/27 auto-closed as invalid on 2021/12/20 07:00
upstream KCSAN: data-race in __stop_tty / pty_write (13) serial 13 4d12h 94d 0/27 moderation: reported on 2024/03/20 09:24
upstream KCSAN: data-race in __stop_tty / pty_write (5) serial 1 819d 819d 0/27 auto-closed as invalid on 2022/04/30 10:57
upstream KCSAN: data-race in __stop_tty / pty_write (10) serial 1 287d 287d 0/27 auto-obsoleted due to no activity on 2023/10/14 11:29
upstream KCSAN: data-race in __stop_tty / pty_write (11) serial 3 244d 247d 0/27 auto-obsoleted due to no activity on 2023/11/26 18:07
upstream KCSAN: data-race in __stop_tty / pty_write (12) serial 7 131d 192d 0/27 auto-obsoleted due to no activity on 2024/03/18 19:09
upstream KCSAN: data-race in __stop_tty / pty_write (7) serial 1 625d 625d 0/27 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 0xffff88813dc379bc of 1 bytes by task 31444 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:2383
 tty_ioctl+0xaf7/0x1130 drivers/tty/tty_io.c:2787
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl+0xcb/0x140 fs/ioctl.c:860
 __x64_sys_ioctl+0x3f/0x50 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff88813dc379bc of 1 bytes by task 9029 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+0x3f6/0x960 kernel/workqueue.c:2307
 worker_thread+0x616/0xa70 kernel/workqueue.c:2454
 kthread+0x1bf/0x1e0 kernel/kthread.c:377
 ret_from_fork+0x1f/0x30

value changed: 0x00 -> 0x01

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 9029 Comm: kworker/u4:46 Not tainted 5.17.0-rc3-syzkaller-00043-gf4bc5bbb5fef-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_unbound flush_to_ldisc
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/02/10 12:11 upstream f4bc5bbb5fef 0b33604d .config console log report info ci2-upstream-kcsan-gce KCSAN: data-race in __stop_tty / pty_write
* Struck through repros no longer work on HEAD.