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:34:41 -0400 [thread overview]
Message-ID: <CAGaAVNUQ1+R7MtUYm2Not1J+pWkkKxQw384RYxAkjCsAuiigFg@mail.gmail.com> (raw)
In-Reply-To: <CAGaAVNUyrQEppHMmTZe_WyohDPEopyupB2iaTj45peeq5qU9vg@mail.gmail.com>
Just happened! so yeah that was it on the trigger. Once Cmac builds
the ko for me I will test it again!
Again thanks so much!
On Mon, May 3, 2021 at 11:32 AM Manojav Sridhar <manojav@manojav.com> wrote:
>
> Ah. Understood. I am not set up to build for freebsd yet ko. But I can
> leave it running on my test box for a bit.
>
> On Mon, May 3, 2021 at 11:31 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> >
> > On Mon, May 3, 2021 at 5:27 PM Manojav Sridhar <manojav@manojav.com> wrote:
> > > 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.
> >
> > Try changing in wg_noise.c:
> >
> > #define HT_INDEX_SIZE (1 << 13)
> >
> > to
> >
> > #define HT_INDEX_SIZE (1 << 3)
> >
> > And then you'll see it hit pretty quickly.
next prev parent reply other threads:[~2021-05-03 15:39 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
2021-05-03 15:30 ` Jason A. Donenfeld
2021-05-03 15:32 ` Manojav Sridhar
2021-05-03 15:34 ` Manojav Sridhar [this message]
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=CAGaAVNUQ1+R7MtUYm2Not1J+pWkkKxQw384RYxAkjCsAuiigFg@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).