From: Manojav Sridhar <manojav@manojav.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
Christian McDonald <rcmcdonald91@gmail.com>
Subject: Re: kp's and mem corruption?
Date: Mon, 3 May 2021 11:27:18 -0400 [thread overview]
Message-ID: <CAGaAVNWDMLAP3FdBPUh33iyVpMSBLTzVEH8_LGXKsS8ebzwjQA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pVOKrLPqD-g1LTe-62_0boi=jQ16WFe6-7deCUJPgyMQ@mail.gmail.com>
Jason,
Thanks for the follow up and bash to script to ensure help re-pro it.
I am guessing my constant restarting of the tunnels when testing the
pfSense based UI we are building triggered the scenario your bash
script creates.
I tried the bash script on both bare metal box and virtualbox pfsense
box. both ran for a few minutes okay. How long does it take to happen?
I am testing with the 0428 snapshot.
Manoj
On Mon, May 3, 2021 at 11:08 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hey again,
>
> Thanks for the .ko you sent me. That was helpful in tracking down the
> bug, which Matt and I have now fixed here:
>
> https://git.zx2c4.com/wireguard-freebsd/commit/?id=c69fb61b94341027ea3c539bcf96d9fe03f65fa5
>
> The commit message includes a little bash reproducer that hit the same
> crash in my tests, making me somewhat confident we squashed the right
> one.
>
> Jason
next prev parent reply other threads:[~2021-05-03 15:31 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
2021-05-03 13:33 ` Manojav Sridhar
2021-05-03 15:08 ` Jason A. Donenfeld
2021-05-03 15:27 ` Manojav Sridhar [this message]
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=CAGaAVNWDMLAP3FdBPUh33iyVpMSBLTzVEH8_LGXKsS8ebzwjQA@mail.gmail.com \
--to=manojav@manojav.com \
--cc=Jason@zx2c4.com \
--cc=rcmcdonald91@gmail.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).