From: "PaX Team" <pageexec@freemail.hu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: imer_setup() is not compatible with PaX's RAP
Date: Tue, 14 Nov 2017 12:12:24 +0100 [thread overview]
Message-ID: <5A0ACF98.2734.3D2AE425@pageexec.freemail.hu> (raw)
In-Reply-To: <CAHmME9prMg_RuEUaO1XNy4Aj6MH3Cu=16kp=F_B-kKbSwO+qdQ@mail.gmail.com>
On 14 Nov 2017 at 10:29, Jason A. Donenfeld wrote:
> I fixed things up here:
> https://git.zx2c4.com/WireGuard/commit/?id=df318d1f0526663a2d92439376379e32ebcfef1a
works fine, thanks.
> > speaking of PaX support, you recently added some __ro_after_init wrapper
> > to wireguard which breaks under KERNEXEC when it's used on ops structs
> > (my __read_only has different semantics) so i have to revert it here but
> > it'd be nicer if you didn't define it when KERNEXEC is active.
>
> So what exactly should I be fixing? I think in that last patch I
> forgot to redefine it to be empty. Would this do what you have in
> mind:
i said 'don't define it', not 'redefine it' ;). the difference is that the
latter removes the definition provided under KERNEXEC.
next prev parent reply other threads:[~2017-11-14 11:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 8:09 Tom Li
2017-11-11 8:16 ` Tom Li
2017-11-12 2:50 ` Jason A. Donenfeld
2017-11-12 3:13 ` Jason A. Donenfeld
2017-11-13 1:39 ` PaX Team
2017-11-13 19:34 ` Jason A. Donenfeld
2017-11-14 0:15 ` PaX Team
2017-11-14 9:29 ` Jason A. Donenfeld
2017-11-14 10:29 ` Jason A. Donenfeld
2017-11-14 11:12 ` PaX Team [this message]
2017-11-28 12:20 ` Jason A. Donenfeld
2017-11-28 12:32 ` PaX Team
2017-11-28 12:36 ` Jason A. Donenfeld
2017-11-28 12:50 ` PaX Team
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=5A0ACF98.2734.3D2AE425@pageexec.freemail.hu \
--to=pageexec@freemail.hu \
--cc=Jason@zx2c4.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).