Hello,
syzbot found the following issue on:
HEAD commit: 0477e928 Linux 5.10-rc7
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=134b6c23500000
kernel config:
https://syzkaller.appspot.com/x/.config?x=329e76890d0bf5c3
dashboard link:
https://syzkaller.appspot.com/bug?extid=fdab22f6fdfe878fbb0a
compiler: clang version 12.0.0 (
https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [
gre...@linuxfoundation.org jiri...@kernel.org linux-...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+fdab22...@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in n_tty_receive_char_inline / n_tty_receive_char_special
read-write to 0xffffc9000150d018 of 8 bytes by task 11062 on cpu 0:
add_echo_byte drivers/tty/n_tty.c:845 [inline]
echo_char drivers/tty/n_tty.c:948 [inline]
n_tty_receive_char_inline+0x418/0x650 drivers/tty/n_tty.c:1420
n_tty_receive_buf_standard drivers/tty/n_tty.c:1583 [inline]
__receive_buf drivers/tty/n_tty.c:1646 [inline]
n_tty_receive_buf_common+0x1892/0x1df0 drivers/tty/n_tty.c:1742
n_tty_receive_buf2+0x2e/0x40 drivers/tty/n_tty.c:1777
tty_ldisc_receive_buf+0x61/0xf0 drivers/tty/tty_buffer.c:461
tty_port_default_receive_buf+0x54/0x80 drivers/tty/tty_port.c:38
receive_buf drivers/tty/tty_buffer.c:481 [inline]
flush_to_ldisc+0x1c5/0x2b0 drivers/tty/tty_buffer.c:533
process_one_work+0x3e1/0x950 kernel/workqueue.c:2272
worker_thread+0x635/0xb90 kernel/workqueue.c:2418
kthread+0x1fd/0x220 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
read to 0xffffc9000150d018 of 8 bytes by task 15863 on cpu 1:
add_echo_byte drivers/tty/n_tty.c:843 [inline]
echo_char drivers/tty/n_tty.c:948 [inline]
eraser drivers/tty/n_tty.c:1043 [inline]
n_tty_receive_char_special+0x10ef/0x3860 drivers/tty/n_tty.c:1316
n_tty_receive_buf_standard drivers/tty/n_tty.c:1584 [inline]
__receive_buf drivers/tty/n_tty.c:1646 [inline]
n_tty_receive_buf_common+0x191b/0x1df0 drivers/tty/n_tty.c:1742
n_tty_receive_buf+0x2b/0x40 drivers/tty/n_tty.c:1771
tiocsti drivers/tty/tty_io.c:2198 [inline]
tty_ioctl+0x8e4/0xfd0 drivers/tty/tty_io.c:2572
vfs_ioctl fs/ioctl.c:48 [inline]
__do_sys_ioctl fs/ioctl.c:753 [inline]
__se_sys_ioctl+0xcb/0x140 fs/ioctl.c:739
__x64_sys_ioctl+0x3f/0x50 fs/ioctl.c:739
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 15863 Comm: syz-executor.0 Not tainted 5.10.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================
---
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.