linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+list8e8dead94ef997c19522@syzkaller.appspotmail.com>
To: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly input report
Date: Tue, 04 Apr 2023 07:19:46 -0700	[thread overview]
Message-ID: <0000000000001632e305f8835e90@google.com> (raw)

Hello input maintainers/developers,

This is a 30-day syzbot report for the input subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/input

During the period, 0 new issues were detected and 0 were fixed.
In total, 14 issues are still open and 42 have been fixed so far.

Some of the still happening issues:

Crashes Repro Title
2162    Yes   WARNING in input_mt_init_slots
              https://syzkaller.appspot.com/bug?extid=0122fa359a69694395d5
93      Yes   WARNING in cm109_urb_irq_callback/usb_submit_urb
              https://syzkaller.appspot.com/bug?extid=2d6d691af5ab4b7e66df
67      Yes   general protection fault in hidraw_release
              https://syzkaller.appspot.com/bug?extid=953a33deaf38c66a915e
49      Yes   inconsistent lock state in find_vmap_area
              https://syzkaller.appspot.com/bug?extid=8d19062486784d15dda9
32      Yes   WARNING in bcm5974_start_traffic/usb_submit_urb
              https://syzkaller.appspot.com/bug?extid=348331f63b034f89b622

---
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.

                 reply	other threads:[~2023-04-04 14:20 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=0000000000001632e305f8835e90@google.com \
    --to=syzbot+list8e8dead94ef997c19522@syzkaller.appspotmail.com \
    --cc=linux-input@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).