All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+list8a8105c4458877154798@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 (Dec 2023)
Date: Sat, 02 Dec 2023 06:45:21 -0800	[thread overview]
Message-ID: <0000000000003087b8060b87eff6@google.com> (raw)

Hello can maintainers/developers,

This is a 31-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, 1 new issues were detected and 0 were fixed.
In total, 9 issues are still open and 47 have been fixed so far.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 281     Yes   possible deadlock in j1939_sk_queue_drop_all
                  https://syzkaller.appspot.com/bug?extid=3bd970a1887812621b4c
<2> 153     No    KMSAN: uninit-value in bpf_prog_run_generic_xdp
                  https://syzkaller.appspot.com/bug?extid=0e6ddb1ef80986bdfe64
<3> 62      Yes   possible deadlock in j1939_session_activate
                  https://syzkaller.appspot.com/bug?extid=f32cbede7fd867ce0d56
<4> 1       Yes   memory leak in j1939_netdev_start
                  https://syzkaller.appspot.com/bug?extid=1d37bef05da87b99c5a6

---
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-12-02 14:45 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=0000000000003087b8060b87eff6@google.com \
    --to=syzbot+list8a8105c4458877154798@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.