From: Peter Whisker <peter.whisker@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard for Windows crash "panic: ring is full" since release of 0.3.10
Date: Tue, 13 Apr 2021 14:01:27 +0100 [thread overview]
Message-ID: <3855f3fb-84ac-cc8f-4a16-3167ae90b381@gmail.com> (raw)
In-Reply-To: <CAHmME9qUXd1iFAbrMfEedaF9C300Tz8e_-B72=hBvEGrmd7cNg@mail.gmail.com>
Hi Jason,
Yes thanks, it's fine again with 0.3.11.
Regards
Peter
On 12/04/2021 18:31, Jason A. Donenfeld wrote:
> Hi Peter,
>
> Please let me know if updating to 0.3.11 fixes the issue.
>
> Jason
prev parent reply other threads:[~2021-04-13 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 0:07 WireGuard for Windows "cq is corrupt" panic in rio_windows.go after insufficient buffer space Joshua Sjoding
2021-04-08 23:13 ` Jason A. Donenfeld
2021-04-08 23:41 ` Joshua Sjoding
2021-04-09 0:22 ` Jason A. Donenfeld
2021-04-09 22:47 ` Jason A. Donenfeld
2021-04-12 7:45 ` WireGuard for Windows crash "panic: ring is full" since release of 0.3.10 Peter Whisker
2021-04-12 7:56 ` Peter Whisker
2021-04-12 8:55 ` Christopher Ng
2021-04-12 17:31 ` Jason A. Donenfeld
2021-04-13 13:01 ` Peter Whisker [this message]
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=3855f3fb-84ac-cc8f-4a16-3167ae90b381@gmail.com \
--to=peter.whisker@gmail.com \
--cc=Jason@zx2c4.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).