Re: general protection fault in n_tty_flush_buffer
This will be essentially same with below one. ioctl(TIOCVHANGUP) versus ioctl(TCSETS) can race. #syz dup: KASAN: user-memory-access Write in n_tty_set_termios
Re: general protection fault in n_tty_flush_buffer
This will be essentially same with below one. ioctl(TIOCVHANGUP) versus ioctl(TCSETS) can race. #syz dup: KASAN: user-memory-access Write in n_tty_set_termios
general protection fault in n_tty_flush_buffer
Hello, syzbot found the following crash on: HEAD commit:e6506eb24187 Merge tag 'trace-v4.17-rc4-2' of git://git.ke.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1295d63780 kernel config: https://syzkaller.appspot.com/x/.config?x=f3b4e30da84ec1ed dashboard link: https://syzkaller.appspot.com/bug?extid=083228748980909eb453 compiler: gcc (GCC) 8.0.1 20180413 (experimental) syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=1340a7c780 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15b25e3780 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+083228748980909eb...@syzkaller.appspotmail.com kasan: CONFIG_KASAN_INLINE enabled kasan: GPF could be caused by NULL-ptr deref or user memory access general protection fault: [#1] SMP KASAN Dumping ftrace buffer: (ftrace buffer empty) Modules linked in: CPU: 1 PID: 4530 Comm: syz-executor147 Not tainted 4.17.0-rc5+ #54 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:reset_buffer_flags drivers/tty/n_tty.c:318 [inline] RIP: 0010:n_tty_flush_buffer+0x64/0x320 drivers/tty/n_tty.c:358 RSP: 0018:8801c60f77a0 EFLAGS: 00010202 RAX: dc00 RBX: RCX: RDX: 044c RSI: 8801ae012ef8 RDI: 2260 RBP: 8801c60f77b8 R08: 7ad5 R09: 0002 R10: 8801ae012f48 R11: 8801ae0126c0 R12: 8801d96321c0 R13: 8801d96323f8 R14: R15: 8801c60f7808 FS: 7f53b10c8700() GS:8801daf0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f53b10a6e78 CR3: 0001ac8cf000 CR4: 001406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: set_termios+0x390/0x7d0 drivers/tty/tty_ioctl.c:404 tty_mode_ioctl+0x265/0xb50 drivers/tty/tty_ioctl.c:745 n_tty_ioctl_helper+0x54/0x3b0 drivers/tty/tty_ioctl.c:940 n_tty_ioctl+0x54/0x320 drivers/tty/n_tty.c:2441 tty_ioctl+0x5e1/0x1870 drivers/tty/tty_io.c:2655 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x1cf/0x16a0 fs/ioctl.c:684 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:701 __do_sys_ioctl fs/ioctl.c:708 [inline] __se_sys_ioctl fs/ioctl.c:706 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:706 do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x445c19 RSP: 002b:7f53b10c7da8 EFLAGS: 0297 ORIG_RAX: 0010 RAX: ffda RBX: 006dac24 RCX: 00445c19 RDX: 2000 RSI: 5404 RDI: 0005 RBP: R08: R09: R10: R11: 0297 R12: 006dac20 R13: 6d74702f7665642f R14: 7f53b10c89c0 R15: 0007 Code: 03 80 3c 02 00 0f 85 b1 02 00 00 49 8b 9c 24 70 05 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d bb 60 22 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 9b 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 RIP: reset_buffer_flags drivers/tty/n_tty.c:318 [inline] RSP: 8801c60f77a0 RIP: n_tty_flush_buffer+0x64/0x320 drivers/tty/n_tty.c:358 RSP: 8801c60f77a0 ---[ end trace 75cd8a017cb978de ]--- --- This bug 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 syzkal...@googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with syzbot. syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches
general protection fault in n_tty_flush_buffer
Hello, syzbot found the following crash on: HEAD commit:e6506eb24187 Merge tag 'trace-v4.17-rc4-2' of git://git.ke.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1295d63780 kernel config: https://syzkaller.appspot.com/x/.config?x=f3b4e30da84ec1ed dashboard link: https://syzkaller.appspot.com/bug?extid=083228748980909eb453 compiler: gcc (GCC) 8.0.1 20180413 (experimental) syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=1340a7c780 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15b25e3780 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+083228748980909eb...@syzkaller.appspotmail.com kasan: CONFIG_KASAN_INLINE enabled kasan: GPF could be caused by NULL-ptr deref or user memory access general protection fault: [#1] SMP KASAN Dumping ftrace buffer: (ftrace buffer empty) Modules linked in: CPU: 1 PID: 4530 Comm: syz-executor147 Not tainted 4.17.0-rc5+ #54 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:reset_buffer_flags drivers/tty/n_tty.c:318 [inline] RIP: 0010:n_tty_flush_buffer+0x64/0x320 drivers/tty/n_tty.c:358 RSP: 0018:8801c60f77a0 EFLAGS: 00010202 RAX: dc00 RBX: RCX: RDX: 044c RSI: 8801ae012ef8 RDI: 2260 RBP: 8801c60f77b8 R08: 7ad5 R09: 0002 R10: 8801ae012f48 R11: 8801ae0126c0 R12: 8801d96321c0 R13: 8801d96323f8 R14: R15: 8801c60f7808 FS: 7f53b10c8700() GS:8801daf0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f53b10a6e78 CR3: 0001ac8cf000 CR4: 001406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: set_termios+0x390/0x7d0 drivers/tty/tty_ioctl.c:404 tty_mode_ioctl+0x265/0xb50 drivers/tty/tty_ioctl.c:745 n_tty_ioctl_helper+0x54/0x3b0 drivers/tty/tty_ioctl.c:940 n_tty_ioctl+0x54/0x320 drivers/tty/n_tty.c:2441 tty_ioctl+0x5e1/0x1870 drivers/tty/tty_io.c:2655 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x1cf/0x16a0 fs/ioctl.c:684 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:701 __do_sys_ioctl fs/ioctl.c:708 [inline] __se_sys_ioctl fs/ioctl.c:706 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:706 do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x445c19 RSP: 002b:7f53b10c7da8 EFLAGS: 0297 ORIG_RAX: 0010 RAX: ffda RBX: 006dac24 RCX: 00445c19 RDX: 2000 RSI: 5404 RDI: 0005 RBP: R08: R09: R10: R11: 0297 R12: 006dac20 R13: 6d74702f7665642f R14: 7f53b10c89c0 R15: 0007 Code: 03 80 3c 02 00 0f 85 b1 02 00 00 49 8b 9c 24 70 05 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d bb 60 22 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 9b 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 RIP: reset_buffer_flags drivers/tty/n_tty.c:318 [inline] RSP: 8801c60f77a0 RIP: n_tty_flush_buffer+0x64/0x320 drivers/tty/n_tty.c:358 RSP: 8801c60f77a0 ---[ end trace 75cd8a017cb978de ]--- --- This bug 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 syzkal...@googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with syzbot. syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches
