All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+list4d04fa20a60bb21c56c5@syzkaller.appspotmail.com>
To: linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
	mkl@pengutronix.de, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly can report
Date: Tue, 04 Apr 2023 07:23:51 -0700	[thread overview]
Message-ID: <000000000000ab085f05f8836ccd@google.com> (raw)

Hello can maintainers/developers,

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

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

Some of the still happening issues:

Crashes Repro Title
1783    Yes   WARNING in j1939_session_deactivate
              https://syzkaller.appspot.com/bug?extid=535e5aae63c0d0433473
502     Yes   WARNING in j1939_session_deactivate_activate_next
              https://syzkaller.appspot.com/bug?extid=3d2eaacbc2b94537c6c5
277     Yes   possible deadlock in j1939_sk_queue_drop_all
              https://syzkaller.appspot.com/bug?extid=3bd970a1887812621b4c
55      No    possible deadlock in j1939_session_activate
              https://syzkaller.appspot.com/bug?extid=f32cbede7fd867ce0d56

---
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:23 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=000000000000ab085f05f8836ccd@google.com \
    --to=syzbot+list4d04fa20a60bb21c56c5@syzkaller.appspotmail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@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.