Development discussion of WireGuard
 help / color / mirror / Atom feed
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: Thu, 6 May 2021 11:59:25 -0400	[thread overview]
Message-ID: <CAGaAVNUgdUmqR0wzh0qo0bwj_4kquhegAzQ5sum4_VMRzpbxsw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pfFUrzAcT26OUnWPvTUgD=PtNc2fV6bz6+N1rOYiyCVg@mail.gmail.com>

Jason,

With some help I was able to get the latest if_wg.ko built. I have
been running the triggering bash script for a while now and not
managed to trigger it. However prior to installing the latest snapshot
it happened one more my on firewall (just provided as FYI) in the
middle of the night as part of normal usage.

Thanks for jumping on this! looking solid again!
Manoj

On Thu, May 6, 2021 at 8:10 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hi Manojav,
>
> 0.0.20210503 is now in ports, which contains these fixes.
>
> Jason

  reply	other threads:[~2021-05-06 15:59 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
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 [this message]
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=CAGaAVNUgdUmqR0wzh0qo0bwj_4kquhegAzQ5sum4_VMRzpbxsw@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).