From: syzbot <syzbot+list02c26f0910ca5bf8710a@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 (Aug 2025)
Date: Mon, 25 Aug 2025 01:44:37 -0700 [thread overview]
Message-ID: <68ac2275.a00a0220.33401d.0403.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, 1 new issues were detected and 2 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> 4212 Yes general protection fault in pcl818_ai_cancel
https://syzkaller.appspot.com/bug?extid=fce5d9d5bd067d6fbe9b
<2> 514 Yes BUG: unable to handle kernel paging request in subdev_8255_io
https://syzkaller.appspot.com/bug?extid=f7ad508e3c76c097483f
<3> 234 Yes BUG: unable to handle kernel paging request in parport_attach
https://syzkaller.appspot.com/bug?extid=c47f45cfb7fc1640ced7
<4> 32 No divide error in comedi_buf_write_free
https://syzkaller.appspot.com/bug?extid=f6c3c066162d2c43a66c
<5> 12 Yes INFO: task hung in comedi_open
https://syzkaller.appspot.com/bug?extid=7811bb68a317954a0347
<6> 8 No BUG: unable to handle kernel NULL pointer dereference in parse_insn
https://syzkaller.appspot.com/bug?extid=ab8008c24e84adee93ff
---
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-08-25 8:44 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=68ac2275.a00a0220.33401d.0403.GAE@google.com \
--to=syzbot+list02c26f0910ca5bf8710a@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 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.