From: syzbot <syzbot+list9fa5fba6c1580c496e3a@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 (Nov 2024)
Date: Mon, 04 Nov 2024 00:50:24 -0800 [thread overview]
Message-ID: <67288ad0.050a0220.35b515.01b7.GAE@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, 0 new issues were detected and 0 were fixed.
In total, 6 issues are still open and 53 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 7872 Yes WARNING: refcount bug in j1939_session_put
https://syzkaller.appspot.com/bug?extid=ad601904231505ad6617
<2> 4947 Yes WARNING: refcount bug in sk_skb_reason_drop
https://syzkaller.appspot.com/bug?extid=d4e8dc385d9258220c31
<3> 3045 Yes WARNING: refcount bug in j1939_xtp_rx_cts
https://syzkaller.appspot.com/bug?extid=5a1281566cc25c9881e0
<4> 523 Yes WARNING: refcount bug in get_taint (2)
https://syzkaller.appspot.com/bug?extid=72d3b151aacf9fa74455
---
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:[~2024-11-04 8:50 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=67288ad0.050a0220.35b515.01b7.GAE@google.com \
--to=syzbot+list9fa5fba6c1580c496e3a@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 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).