From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: k@vodka.home.kg
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] mips32 crash
Date: Sun, 6 Nov 2016 12:20:34 +0100 [thread overview]
Message-ID: <CAHmME9oc=_cX3XPo0VBYx70HF-9D85TLivFWU4jdadKcfzTgmA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9odjXbgoTFfPzu-1rtTxrT-kEucYeevHgHHzJnd-NTCyQ@mail.gmail.com>
> <7>[13905.531148] wireguard: Sending handshake initiation to peer 1 (x.x.x.x:16)
> <4>[13905.629622] ------------[ cut here ]------------
So you said the crash 100% occurs 100ms after sending handshake
initiation. If related this could be because:
a) The scheduler ticks come in 100ms intervals. In this case, the
crash would be caused by something in sending the initiation.
or
b) The ping latency is 100ms. In this case, the crash would be caused
by something in receiving the response.
or
c) Something else.
I'm curious: when the crash happens, does the ARM box receive the
handshake initiation message?
next prev parent reply other threads:[~2016-11-06 11:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 7:02 k
2016-11-06 8:07 ` k
2016-11-06 10:18 ` Jason A. Donenfeld
2016-11-06 10:20 ` Jason A. Donenfeld
2016-11-06 10:55 ` Jason A. Donenfeld
2016-11-06 11:20 ` Jason A. Donenfeld [this message]
2016-11-06 12:16 ` Jason A. Donenfeld
2016-11-06 12:22 ` Jason A. Donenfeld
2016-11-07 2:06 ` Jason A. Donenfeld
2016-11-07 8:37 ` Baptiste Jonglez
2016-11-07 10:22 ` Jason A. Donenfeld
2016-11-07 10:02 ` k
2016-11-07 10:30 ` Jason A. Donenfeld
2016-11-09 9:56 ` k
[not found] ` <7365258.20161107095446@vodka.home.kg>
2016-11-07 10:26 ` Jason A. Donenfeld
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='CAHmME9oc=_cX3XPo0VBYx70HF-9D85TLivFWU4jdadKcfzTgmA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=k@vodka.home.kg \
--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).