From: syzbot <syzbot+listd50f3c6120445dc61e8f@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly serial report (Jan 2025)
Date: Fri, 17 Jan 2025 02:36:26 -0800 [thread overview]
Message-ID: <678a32aa.050a0220.20d369.005b.GAE@google.com> (raw)
Hello serial maintainers/developers,
This is a 31-day syzbot report for the serial subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/serial
During the period, 0 new issues were detected and 0 were fixed.
In total, 18 issues are still open and 44 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 704 Yes KMSAN: uninit-value in n_tty_receive_buf_standard
https://syzkaller.appspot.com/bug?extid=559c7fe4b8bac56d38c2
<2> 469 No INFO: task hung in console_callback (5)
https://syzkaller.appspot.com/bug?extid=1fb20cf68d15e7c2388d
<3> 172 Yes INFO: task can't die in show_free_areas
https://syzkaller.appspot.com/bug?extid=8f41dccfb6c03cc36fd6
<4> 86 Yes KASAN: slab-use-after-free Read in tty_write_room (2)
https://syzkaller.appspot.com/bug?extid=2a81fdd5c6ddffee3894
<5> 77 Yes BUG: soft lockup in tx
https://syzkaller.appspot.com/bug?extid=5e87db90e68fbc4707c6
<6> 55 Yes KMSAN: uninit-value in n_tty_receive_buf_closing (3)
https://syzkaller.appspot.com/bug?extid=dd514b5f0cf048aec256
<7> 31 Yes possible deadlock in tty_buffer_flush (3)
https://syzkaller.appspot.com/bug?extid=52cf91760dcb1dac6376
<8> 14 No KMSAN: uninit-value in n_tty_lookahead_flow_ctrl (2)
https://syzkaller.appspot.com/bug?extid=290abdcd4f509377a0eb
<9> 12 No general protection fault in n_tty_receive_buf_common (2)
https://syzkaller.appspot.com/bug?extid=2dda672e146ff12ccb02
<10> 6 Yes INFO: task hung in paste_selection (2)
https://syzkaller.appspot.com/bug?extid=275e275bd3f536725dd8
---
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 syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2025-01-17 10:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=678a32aa.050a0220.20d369.005b.GAE@google.com \
--to=syzbot+listd50f3c6120445dc61e8f@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.