From: syzbot <syzbot+listd934ed408c9f32a4a743@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wireguard@lists.zx2c4.com
Subject: [syzbot] Monthly wireguard report (Aug 2023)
Date: Mon, 21 Aug 2023 13:40:51 -0700 [thread overview]
Message-ID: <000000000000e8eb14060374e429@google.com> (raw)
Hello wireguard maintainers/developers,
This is a 31-day syzbot report for the wireguard subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/wireguard
During the period, 2 new issues were detected and 0 were fixed.
In total, 6 issues are still open and 14 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 763 No KCSAN: data-race in wg_packet_send_staged_packets / wg_packet_send_staged_packets (3)
https://syzkaller.appspot.com/bug?extid=6ba34f16b98fe40daef1
<2> 511 No KCSAN: data-race in wg_packet_decrypt_worker / wg_packet_rx_poll (2)
https://syzkaller.appspot.com/bug?extid=d1de830e4ecdaac83d89
<3> 3 Yes INFO: rcu detected stall in wg_ratelimiter_gc_entries (2)
https://syzkaller.appspot.com/bug?extid=c1cc0083f159b67cb192
---
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-21 20:43 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=000000000000e8eb14060374e429@google.com \
--to=syzbot+listd934ed408c9f32a4a743@syzkaller.appspotmail.com \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wireguard@lists.zx2c4.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).