Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Manojav Sridhar <manojav@manojav.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 17:35:01 +0200	[thread overview]
Message-ID: <CAHmME9qLmvt7wRSucwZuV5R6y1xOYxhy_UO_GANu2t6-tOY_zQ@mail.gmail.com> (raw)
In-Reply-To: <CAGaAVNUyrQEppHMmTZe_WyohDPEopyupB2iaTj45peeq5qU9vg@mail.gmail.com>

On Mon, May 3, 2021 at 5:33 PM 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.

Ah, don't worry about it. The trigger was sufficient for my purposes,
but it doesn't need to be reproduced elsewhere necessarily. However,
if you do wind up seeing this same bug again, using the latest master
branch that contains the fix, please let me know, since that'd
indicate I've done something wrong.

Jason

      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
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 [this message]

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=CAHmME9qLmvt7wRSucwZuV5R6y1xOYxhy_UO_GANu2t6-tOY_zQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=manojav@manojav.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).