From: Eddie Kovsky <ewk@edkovsky.org>
To: jeyu@redhat.com, rusty@rustcorp.com.au, keescook@chromium.org,
kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com
Cc: linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com
Subject: [PATCH v2 0/3] provide check for ro_after_init memory sections
Date: Fri, 17 Feb 2017 22:58:41 -0700 [thread overview]
Message-ID: <20170218055844.1457-1-ewk@edkovsky.org> (raw)
Provide a mechansim for other functions to verify that their arguments
are read-only. Use this mechansim in the vmbus register functions to
reject arguments that fail this test.
This implements a suggestion made by Kees Cook for the Kernel Self
Protection Project:
* provide mechanism to check for ro_after_init memory areas, and
reject structures not marked ro_after_init in vmbus_register()
http://www.openwall.com/lists/kernel-hardening/2017/02/04/1
I have successfully compiled this series on next-20170215 for x86.
Eddie Kovsky (3):
module: verify address is read-only
extable: verify address is read-only
Make vmbus register arguments read-only
drivers/hv/vmbus_drv.c | 10 ++++++++++
include/linux/kernel.h | 2 ++
include/linux/module.h | 7 +++++++
kernel/extable.c | 29 +++++++++++++++++++++++++++++
kernel/module.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 92 insertions(+)
--
2.11.1
next reply other threads:[~2017-02-18 6:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 5:58 Eddie Kovsky [this message]
2017-02-18 5:58 ` [PATCH v2 1/3] module: verify address is read-only Eddie Kovsky
2017-02-20 17:14 ` Stephen Hemminger
2017-02-21 20:32 ` Kees Cook
2017-02-21 20:51 ` Stephen Hemminger
2017-02-26 17:42 ` Jessica Yu
2017-02-18 5:58 ` [PATCH v2 2/3] extable: " Eddie Kovsky
2017-02-18 6:33 ` kbuild test robot
2017-02-18 6:49 ` kbuild test robot
2017-02-18 5:58 ` [PATCH v2 3/3] Make vmbus register arguments read-only Eddie Kovsky
2017-02-18 6:30 ` kbuild test robot
2017-02-18 8:55 ` kbuild test robot
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=20170218055844.1457-1-ewk@edkovsky.org \
--to=ewk@edkovsky.org \
--cc=haiyangz@microsoft.com \
--cc=jeyu@redhat.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sthemmin@microsoft.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
all inboxes | Powered by JetHome®