wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Joshua Sjoding <joshua.sjoding@scjalliance.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard for Windows "cq is corrupt" panic in rio_windows.go after insufficient buffer space
Date: Thu, 8 Apr 2021 17:13:39 -0600	[thread overview]
Message-ID: <CAHmME9qYHttPgwranGbUS4ijQOde96Je-f2VAM94LMvsNqSfVw@mail.gmail.com> (raw)
In-Reply-To: <CALaUSusmdvz2XAT6c24023dZroTwVPKr0k7S+y6YVAXW1-ubJw@mail.gmail.com>

Hi Joshua,

Thanks for the log. It seems like Windows' Registered I/O extensions
still are causing issues...

Is the log that you sent me "complete"? I'm asking because it appears
there are only 2032 WSAENOBUFS lines, rather than the 2048 or 2047 or
2049 that I'd expect to see.

Jason

  reply	other threads:[~2021-04-08 23:15 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 [this message]
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

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=CAHmME9qYHttPgwranGbUS4ijQOde96Je-f2VAM94LMvsNqSfVw@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=joshua.sjoding@scjalliance.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).