From: syzbot <syzbot+list3b7ff8aa9cee9123dcec@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 (Jan 2024)
Date: Wed, 17 Jan 2024 14:20:23 -0800 [thread overview]
Message-ID: <00000000000034f719060f2ba746@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, 4 issues are still open and 15 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 841 No KCSAN: data-race in wg_packet_send_staged_packets / wg_packet_send_staged_packets (3)
https://syzkaller.appspot.com/bug?extid=6ba34f16b98fe40daef1
<2> 1 No KCSAN: data-race in wg_packet_handshake_receive_worker / wg_packet_rx_poll (7)
https://syzkaller.appspot.com/bug?extid=97d9596e4ae0572c9825
<3> 1 No KCSAN: data-race in wg_packet_send_keepalive / wg_packet_send_staged_packets (6)
https://syzkaller.appspot.com/bug?extid=6d5c91ea71454cf3e972
---
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-01-17 22:24 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=00000000000034f719060f2ba746@google.com \
--to=syzbot+list3b7ff8aa9cee9123dcec@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).