From: Manojav Sridhar <manojav@manojav.com>
To: wireguard@lists.zx2c4.com
Subject: kp's and mem corruption?
Date: Sun, 2 May 2021 17:44:04 -0400 [thread overview]
Message-ID: <CAGaAVNVPhaXnRyS8TaNddNEGJqGBcW=5cWyb1c=vV0yeOovwqQ@mail.gmail.com> (raw)
Hi Jason,
Great work on the Freebsd kmod so far!
Couple of issues to report. I am running the wireguard-kmod-0.0.20210428
snapshot on my pfsense router. I am working with the pfSense-pkg-Wireguard
effort in building the WG package. Admittedly I am mostly testing and
providing some UI code. However I have come across 2 errors. First one is
a KP that happened sometime today.
FreeBSD pfsense 12.2-STABLE FreeBSD 12.2-STABLE
1b709158e581(RELENG_2_5_0) pfSense amd64
Here is the stack trace from the KP https://pastebin.com/4bjdzYas
db:0:kdb.enter.default> bt
Tracing pid 0 tid 100402 td 0xfffff800c67b6740
kdb_enter() at kdb_enter+0x37/frame 0xfffffe004d02c4b0
vpanic() at vpanic+0x197/frame 0xfffffe004d02c500
panic() at panic+0x43/frame 0xfffffe004d02c560
trap_fatal() at trap_fatal+0x391/frame 0xfffffe004d02c5c0
trap() at trap+0x67/frame 0xfffffe004d02c6d0
calltrap() at calltrap+0x8/frame 0xfffffe004d02c6d0
--- trap 0x9, rip = 0xffffffff840fd580, rsp = 0xfffffe004d02c7a0, rbp =
0xfffffe004d02c7e0 ---
noise_remote_index_insert() at noise_remote_index_insert+0xb0/frame
0xfffffe004d02c7e0
noise_consume_initiation() at noise_consume_initiation+0x6bb/frame
0xfffffe004d02ca10
wg_softc_handshake_receive() at wg_softc_handshake_receive+0x27a/frame
0xfffffe004d02cb20
gtaskqueue_run_locked() at gtaskqueue_run_locked+0x121/frame
0xfffffe004d02cb80
gtaskqueue_thread_loop() at gtaskqueue_thread_loop+0xb6/frame
0xfffffe004d02cbb0
fork_exit() at fork_exit+0x7e/frame 0xfffffe004d02cbf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe004d02cbf0
Second issue is that I am seeing memory silent corruption where the pfSense
UI stops responding and serves up invalid files. Reboot fixes it. I have
NOT noticed this issue with the 0415 snapshot; this happened both in the
0424 and 0428 snapshots. While I cannot definitively say its wg related,
that is the only bit changing on the boxes.
Thanks
Manoj
next reply other threads:[~2021-05-03 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 21:44 Manojav Sridhar [this message]
2021-05-03 13:07 ` Jason A. Donenfeld
2021-05-03 13:33 ` Manojav Sridhar
2021-05-03 15:08 ` Jason A. Donenfeld
2021-05-03 15:27 ` Manojav Sridhar
2021-05-03 15:30 ` Jason A. Donenfeld
2021-05-03 15:32 ` Manojav Sridhar
2021-05-03 15:34 ` Manojav Sridhar
2021-05-03 15:35 ` Jason A. Donenfeld
2021-05-03 15:36 ` Manojav Sridhar
2021-05-03 17:56 ` Jason A. Donenfeld
2021-05-03 19:53 ` Manojav Sridhar
2021-05-06 12:10 ` Jason A. Donenfeld
2021-05-06 15:59 ` Manojav Sridhar
2021-05-03 15:35 ` 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='CAGaAVNVPhaXnRyS8TaNddNEGJqGBcW=5cWyb1c=vV0yeOovwqQ@mail.gmail.com' \
--to=manojav@manojav.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).