From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: nsajko@gmail.com
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] device: in setZero, keep arr alive after being written to
Date: Tue, 27 Aug 2019 16:54:57 -0600 [thread overview]
Message-ID: <CAHmME9pDABPALZ+P+3TO20FTcwu1Gni3ZumP-Y+nB6aHjBPO1w@mail.gmail.com> (raw)
In-Reply-To: <5d41995d.1c69fb81.35aae.ce0c@mx.google.com>
But this doesn't prevent the runtime from copying things to places we
can't control, right?
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-08-27 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 13:36 [PATCH] device: in setZero, keep arr alive after being written to nsajko
2019-08-27 22:54 ` Jason A. Donenfeld [this message]
2019-08-27 23:02 ` Neven Sajko
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=CAHmME9pDABPALZ+P+3TO20FTcwu1Gni3ZumP-Y+nB6aHjBPO1w@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=nsajko@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).