Development discussion of WireGuard
 help / color / mirror / Atom feed
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: Mon, 7 Nov 2016 11:30:11 +0100	[thread overview]
Message-ID: <CAHmME9r4PirMW2ASZSdxrHkJu2bMbbNGbR7ba+DpA1_JeN+Dug@mail.gmail.com> (raw)
In-Reply-To: <1522436030.20161107130256@vodka.home.kg>

Hey k,

> So , guys, I found where shit lies !
> Crash happens only when l2tp is involved.
> I reproduced crash in the following scenario :
>
> Windows ETH -> ETH Dlink ETH L2TP WG -> WG L2TP ETH Ubuntu

Brilliant!

Are you able to trigger this with ordinary iperf? Or just CIFS?

Are you able to trigger this with just host-host l2tp, or do you need
to be forwarding packets?

Can you reproduce this on an x86 kernel running KASAN and the various
debug options in:
https://git.zx2c4.com/WireGuard/tree/src/tests/qemu/debug.config

Thanks for triaging this so far. It's coming along well...

Talk soon,
Jason

  reply	other threads:[~2016-11-07 10:28 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
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 [this message]
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=CAHmME9r4PirMW2ASZSdxrHkJu2bMbbNGbR7ba+DpA1_JeN+Dug@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).