From: syzbot <syzbot+list0119abf18c5d23a8a062@syzkaller.appspotmail.com>
To: abbotti@mev.co.uk, hsweeten@visionengravers.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly comedi report (Sep 2025)
Date: Wed, 24 Sep 2025 05:39:34 -0700 [thread overview]
Message-ID: <68d3e686.a70a0220.4f78.0024.GAE@google.com> (raw)
Hello comedi maintainers/developers,
This is a 31-day syzbot report for the comedi subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/comedi
During the period, 0 new issues were detected and 0 were fixed.
In total, 11 issues are still open and 8 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 7563 Yes general protection fault in pcl818_ai_cancel
https://syzkaller.appspot.com/bug?extid=fce5d9d5bd067d6fbe9b
<2> 772 Yes BUG: unable to handle kernel paging request in subdev_8255_io
https://syzkaller.appspot.com/bug?extid=f7ad508e3c76c097483f
<3> 349 Yes BUG: unable to handle kernel paging request in parport_attach
https://syzkaller.appspot.com/bug?extid=c47f45cfb7fc1640ced7
<4> 28 No divide error in comedi_inc_scan_progress
https://syzkaller.appspot.com/bug?extid=af53dea94b16396bc646
<5> 13 Yes INFO: task hung in comedi_open
https://syzkaller.appspot.com/bug?extid=7811bb68a317954a0347
---
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-09-24 12:39 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=68d3e686.a70a0220.4f78.0024.GAE@google.com \
--to=syzbot+list0119abf18c5d23a8a062@syzkaller.appspotmail.com \
--cc=abbotti@mev.co.uk \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®