All of lore.kernel.org
 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: Mon, 3 May 2021 15:53:51 -0400	[thread overview]
Message-ID: <CAGaAVNXqqvdxWOO7Yr4Zrjh_Z-O8kCkbGJguhs=bD04CA=n_eQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9oTyAAbEmu1-7Mv-tx6UxnXTa3-i6=+fro84U286h+RMg@mail.gmail.com>

Jason,

Thanks for the update. Yes it still triggers this on the current
snapshot, which is built prior to your fix. I will retry it once you
release a new snapshot. It seems quite a long shot that this occurred
on my firewall in the first place. Glad it was reported and fixed.
Onward!


Thanks
Manoj



On Mon, May 3, 2021 at 1:56 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> The code in here will repro the bug much faster:
>
> https://git.zx2c4.com/wireguard-freebsd/commit/?id=561f3a8f930cf2e44f493fa04d932ba9a2362cc5

  reply	other threads:[~2021-05-03 19:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 21:44 kp's and mem corruption? 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 [this message]
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='CAGaAVNXqqvdxWOO7Yr4Zrjh_Z-O8kCkbGJguhs=bD04CA=n_eQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.