From: Shachar Shemesh <shachar@shemesh.biz>
To: Lev Olshvang <levonshe@yandex.com>,
linux-il <linux-il@cs.huji.ac.il>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: How to forbid user space and kernel executable pages from becoming writable?
Date: Sat, 5 Jan 2019 22:22:31 +0200 [thread overview]
Message-ID: <7a371c33-269d-27ce-82d0-b4620f90b1e6@shemesh.biz> (raw)
In-Reply-To: <33504091546702201@myt2-cd7fa496c4f7.qloud-c.yandex.net>
[-- Attachment #1: Type: text/html, Size: 5157 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-01-08 2:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 15:30 How to forbid user space and kernel executable pages from becoming writable? Lev Olshvang
2019-01-05 20:22 ` Shachar Shemesh [this message]
2019-01-05 20:35 ` valdis.kletnieks
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=7a371c33-269d-27ce-82d0-b4620f90b1e6@shemesh.biz \
--to=shachar@shemesh.biz \
--cc=kernelnewbies@kernelnewbies.org \
--cc=levonshe@yandex.com \
--cc=linux-il@cs.huji.ac.il \
/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).