From: syzbot <syzbot+listfbbd0645f826b13f6b41@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 (Aug 2023)
Date: Sun, 27 Aug 2023 07:06:05 -0700 [thread overview]
Message-ID: <0000000000002106de0603e814ef@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, 1 new issues were detected and 0 were fixed.
In total, 13 issues are still open and 40 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3604 Yes BUG: sleeping function called from invalid context in console_lock (2)
https://syzkaller.appspot.com/bug?extid=dbac96d8e73b61aa559c
<2> 39 Yes general protection fault in serial8250_tx_chars
https://syzkaller.appspot.com/bug?extid=837b8c9032c053262db8
<3> 16 Yes BUG: sleeping function called from invalid context in gsm_send
https://syzkaller.appspot.com/bug?extid=b687fe9bf10db0839715
<4> 4 Yes memory leak in gsmld_ioctl
https://syzkaller.appspot.com/bug?extid=6e3e8f30f269f5028e5d
<5> 1 Yes INFO: rcu detected stall in console_callback
https://syzkaller.appspot.com/bug?extid=32af18ae7b894a681f2d
---
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:[~2023-08-27 14:10 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=0000000000002106de0603e814ef@google.com \
--to=syzbot+listfbbd0645f826b13f6b41@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