From: syzbot <syzbot+listd327a02095ed68308eae@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Jul 2023)
Date: Tue, 01 Aug 2023 05:53:54 -0700 [thread overview]
Message-ID: <0000000000001f92630601dc0a7f@google.com> (raw)
Hello net maintainers/developers,
This is a 31-day syzbot report for the net subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/net
During the period, 8 new issues were detected and 2 were fixed.
In total, 86 issues are still open and 1285 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 6491 Yes WARNING in dev_watchdog (2)
https://syzkaller.appspot.com/bug?extid=d55372214aff0faa1f1f
<2> 3755 Yes KMSAN: uninit-value in eth_type_trans (2)
https://syzkaller.appspot.com/bug?extid=0901d0cc75c3d716a3a3
<3> 1446 Yes KMSAN: uninit-value in __skb_checksum_complete (5)
https://syzkaller.appspot.com/bug?extid=b024befb3ca7990fea37
<4> 868 Yes possible deadlock in __dev_queue_xmit (3)
https://syzkaller.appspot.com/bug?extid=3b165dac15094065651e
<5> 846 Yes INFO: task hung in switchdev_deferred_process_work (2)
https://syzkaller.appspot.com/bug?extid=8ecc009e206a956ab317
<6> 552 Yes INFO: task hung in rtnetlink_rcv_msg
https://syzkaller.appspot.com/bug?extid=8218a8a0ff60c19b8eae
<7> 528 Yes KMSAN: uninit-value in IP6_ECN_decapsulate
https://syzkaller.appspot.com/bug?extid=bf7e6250c7ce248f3ec9
<8> 529 No KMSAN: uninit-value in __hw_addr_add_ex
https://syzkaller.appspot.com/bug?extid=cec7816c907e0923fdcc
<9> 364 Yes BUG: MAX_LOCKDEP_ENTRIES too low! (3)
https://syzkaller.appspot.com/bug?extid=b04c9ffbbd2f303d00d9
<10> 348 Yes INFO: rcu detected stall in corrupted (4)
https://syzkaller.appspot.com/bug?extid=aa7d098bd6fa788fae8e
---
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-08-01 12:53 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=0000000000001f92630601dc0a7f@google.com \
--to=syzbot+listd327a02095ed68308eae@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).