From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "dxiri@xirihosting.com" <dxiri@xirihosting.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
ElRepo <contact@elrepo.org>
Subject: Re: Kernel Panic after updating Kernel
Date: Wed, 17 Jun 2020 02:32:36 -0600 [thread overview]
Message-ID: <CAHmME9oz5tt9u5S3V6JikvB3oGihXR5rcZTLvcjxNu4qnvWCOw@mail.gmail.com> (raw)
In-Reply-To: <1592249458.376720421@webmail.emailsrvr.com>
Hi Diego,
On Wed, Jun 17, 2020 at 2:01 AM dxiri@xirihosting.com
<dxiri@xirihosting.com> wrote:
>
> Posted this on IRC but got no response, probably this will be a better place:
>
> I updated my Centos7 server yesterday and wireguard is causing a kernel panic, wanted to know if this is a known issue?
>
> Using kernel 3.10.0-1127.10.1.el7.x86_64
>
> I Tried with 2 different repos (elrepo and Copr repo for wireguard owned by jdoss) and I have the same issue.
>
> I took a screenshot of The kernel panic and uploaded at https://imgur.com/a/Ojxeor0
>
> Another interesting bit of info is that as long as I don't move traffic trough wg0 vnic, no panic happens. I can easily trigger the panic by just doing a ping to the other VPN endpoint and I am able to reproduce this every single time.
>
> # lsmod | grep -i wire
> wireguard 200896 0
> ip6_udp_tunnel 12755 1 wireguard
> udp_tunnel 14423 1 wireguard
>
> Thanks for the help!
> Diego
Huh, that's funny -- I'm unable to reproduce the bug at all.
Does running this script crash for you?
https://salsa.debian.org/debian/wireguard-linux-compat/-/raw/debian/master/debian/tests/netns-mini
If not, could you describe your setup more and maybe some repro steps for me?
Thanks,
Jason
next prev parent reply other threads:[~2020-06-17 8:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 19:30 dxiri
2020-06-17 8:32 ` Jason A. Donenfeld [this message]
2020-06-18 4:31 ` dxiri
2020-06-18 5:53 ` Jason A. Donenfeld
2020-06-18 16:48 ` Jean-Denis Girard
2020-06-18 19:27 ` Jason A. Donenfeld
2020-06-18 19:48 ` Jason A. Donenfeld
2020-06-18 20:10 ` Jean-Denis Girard
2020-06-18 20:11 ` Jason A. Donenfeld
2020-06-19 6:58 ` Jean-Dens Girard
2020-06-19 7:38 ` Jason A. Donenfeld
2020-06-27 1:26 ` Jean-Denis Girard
[not found] ` <975a5f77-5c7e-dcfe-6bbe-d4b6e2c5e379@53c70r.de>
2020-06-21 12:57 ` Silvan Nagl
2020-06-18 11:02 ` Phil Perry
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=CAHmME9oz5tt9u5S3V6JikvB3oGihXR5rcZTLvcjxNu4qnvWCOw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=contact@elrepo.org \
--cc=dxiri@xirihosting.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).