From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Manojav Sridhar <manojav@manojav.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: kp's and mem corruption?
Date: Mon, 3 May 2021 15:07:15 +0200 [thread overview]
Message-ID: <CAHmME9o+aSX5f_KZ9UKWNdKUwpjnMU3iKn1e8bBdTvsDCqfceg@mail.gmail.com> (raw)
In-Reply-To: <CAGaAVNVPhaXnRyS8TaNddNEGJqGBcW=5cWyb1c=vV0yeOovwqQ@mail.gmail.com>
Hi Manojav,
On Mon, May 3, 2021 at 3:05 PM Manojav Sridhar <manojav@manojav.com> wrote:
> --- 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
Do you know how to reproduce this? Do you have the symbol file
anywhere? Otherwise, do you think you could send me (off list) your
if_wg.ko file that produced this stack trace? Then I can put it into
the disassembler.
> Second issue is that I am seeing memory silent corruption where the pfSense
> UI stops responding and serves up invalid files.
Fixed in https://lists.zx2c4.com/pipermail/wireguard/2021-May/006694.html .
Jason
next prev parent reply other threads:[~2021-05-03 13:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 21:44 Manojav Sridhar
2021-05-03 13:07 ` Jason A. Donenfeld [this message]
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=CAHmME9o+aSX5f_KZ9UKWNdKUwpjnMU3iKn1e8bBdTvsDCqfceg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=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).