wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel panic on 5.3.1-arch1-1-ARCH
Date: Sat, 05 Oct 2019 23:20:19 +0200	[thread overview]
Message-ID: <87r23qc2jw.fsf@ungleich.ch> (raw)
In-Reply-To: <CAHmME9rHYf71vrPxVec5AVaUOgB=+1YHE+j8rg=ebDbZO0qA2g@mail.gmail.com>


Hey Jason,

thanks for the quick reply - I' ll upgrade as soon as a new package is
released and give a status update afterwards. Thanks for tracking it
down!

Best,

Nico

Jason A. Donenfeld <Jason@zx2c4.com> writes:

> This isn't WireGuard, actually. It's a line in wg-quick's bash that
> says `ip rule add ... suppress_prefix ...`.
>
> You can reproduce the kernel crash without WireGuard anywhere in the
> equation with this sequence:
>
> ip netns add crash
> ip -n crash link add dummy1 type dummy
> ip -n crash link set dummy1 up
> ip -n crash -6 route add default dev dummy1
> ip -n crash -6 rule add table main suppress_prefixlength 0
> ip netns exec crash ping -f -c 1000 -W 1 1234::1 || true
> ip -n crash -6 rule del table main suppress_prefixlength 0
> ip -n crash link del dummy1
> ip netns del crash
>
> I submitted a patch for this upstream here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=ca7a03c4175366a92cee0ccc4fec0038c3266e26
>
> It's been backported to stable already. Update your kernel to 5.3.4
> and things should work again for you.
>
> Jason


--
Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-10-05 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05 20:45 Kernel panic on 5.3.1-arch1-1-ARCH Nico Schottelius
2019-10-05 20:57 ` Jason A. Donenfeld
2019-10-05 21:20   ` Nico Schottelius [this message]
2019-10-05 22:02     ` Nico Schottelius

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=87r23qc2jw.fsf@ungleich.ch \
    --to=nico.schottelius@ungleich.ch \
    --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).