From: syzbot <syzbot+listbb8340e4e1f8191bee93@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 (Feb 2024)
Date: Fri, 02 Feb 2024 13:05:23 -0800 [thread overview]
Message-ID: <00000000000074375c06106c787f@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, 3 new issues were detected and 0 were fixed.
In total, 16 issues are still open and 40 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 51656 Yes possible deadlock in console_flush_all (2)
https://syzkaller.appspot.com/bug?extid=f78380e4eae53c64125c
<2> 4747 Yes BUG: sleeping function called from invalid context in console_lock (2)
https://syzkaller.appspot.com/bug?extid=dbac96d8e73b61aa559c
<3> 207 Yes KMSAN: uninit-value in n_tty_receive_buf_standard
https://syzkaller.appspot.com/bug?extid=559c7fe4b8bac56d38c2
<4> 121 Yes KASAN: stack-out-of-bounds Read in sched_show_task
https://syzkaller.appspot.com/bug?extid=8d2757d62d403b2d9275
<5> 73 Yes general protection fault in serial8250_tx_chars
https://syzkaller.appspot.com/bug?extid=837b8c9032c053262db8
<6> 60 Yes BUG: soft lockup in tx
https://syzkaller.appspot.com/bug?extid=5e87db90e68fbc4707c6
<7> 36 Yes INFO: task can't die in show_free_areas
https://syzkaller.appspot.com/bug?extid=8f41dccfb6c03cc36fd6
<8> 6 Yes INFO: task hung in paste_selection (2)
https://syzkaller.appspot.com/bug?extid=275e275bd3f536725dd8
<9> 2 No KASAN: slab-use-after-free Read in tty_write_room (2)
https://syzkaller.appspot.com/bug?extid=2a81fdd5c6ddffee3894
---
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.
next reply other threads:[~2024-02-02 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 21:05 syzbot [this message]
2024-02-05 8:09 ` [syzbot] Monthly serial report (Feb 2024) Tony Lindgren
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=00000000000074375c06106c787f@google.com \
--to=syzbot+listbb8340e4e1f8191bee93@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).