From: Kees Cook <keescook@chromium.org>
To: kernel-hardening@lists.openwall.com
Cc: Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Jiri Slaby <jslaby@suse.cz>, Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] lkdtm: add usercopy and rodata, fix atomic
Date: Tue, 7 Jun 2016 14:57:03 -0700 [thread overview]
Message-ID: <1465336628-18219-1-git-send-email-keescook@chromium.org> (raw)
This adds several new tests to lkdtm.
To test non-executability of .rodata, lkdtm's build method shifted
around a bit requiring a source file rename. But after some objcopy
magic, there is now an architecture-agnostic way to write functions
into .rodata.
The atomic under/overflow test was split so that each case could be
individually tested.
The biggest addition are the usercopy tests (in preparation for
CONFIG_HARDENED_USERCOPY, based on grsecurity/PaX's PAX_USERCOPY).
This tests both directions (copy_to_from, copy_from_user) of the
three error conditions that are checked for: wrong object size,
wrong stack frame, and wrong object markings.
Unless anyone has blocking comments, I'll send a pull to Greg
for this to land in -next soon.
-Kees
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: kernel-hardening@lists.openwall.com
Cc: Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Jiri Slaby <jslaby@suse.cz>, Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org
Subject: [kernel-hardening] [PATCH 0/5] lkdtm: add usercopy and rodata, fix atomic
Date: Tue, 7 Jun 2016 14:57:03 -0700 [thread overview]
Message-ID: <1465336628-18219-1-git-send-email-keescook@chromium.org> (raw)
This adds several new tests to lkdtm.
To test non-executability of .rodata, lkdtm's build method shifted
around a bit requiring a source file rename. But after some objcopy
magic, there is now an architecture-agnostic way to write functions
into .rodata.
The atomic under/overflow test was split so that each case could be
individually tested.
The biggest addition are the usercopy tests (in preparation for
CONFIG_HARDENED_USERCOPY, based on grsecurity/PaX's PAX_USERCOPY).
This tests both directions (copy_to_from, copy_from_user) of the
three error conditions that are checked for: wrong object size,
wrong stack frame, and wrong object markings.
Unless anyone has blocking comments, I'll send a pull to Greg
for this to land in -next soon.
-Kees
next reply other threads:[~2016-06-07 21:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 21:57 Kees Cook [this message]
2016-06-07 21:57 ` [kernel-hardening] [PATCH 0/5] lkdtm: add usercopy and rodata, fix atomic Kees Cook
2016-06-07 21:57 ` [PATCH 1/5] lkdtm: split build into multiple source files Kees Cook
2016-06-07 21:57 ` [kernel-hardening] " Kees Cook
2016-06-07 21:57 ` [PATCH 2/5] lkdtm: clean up after rename Kees Cook
2016-06-07 21:57 ` [kernel-hardening] " Kees Cook
2016-06-07 21:57 ` [PATCH 3/5] lkdtm: add function for testing .rodata section Kees Cook
2016-06-07 21:57 ` [kernel-hardening] " Kees Cook
2016-06-08 1:02 ` Laura Abbott
2016-06-08 1:02 ` [kernel-hardening] " Laura Abbott
2016-06-08 15:46 ` Kees Cook
2016-06-08 15:46 ` [kernel-hardening] " Kees Cook
2016-06-08 16:15 ` Laura Abbott
2016-06-08 16:15 ` [kernel-hardening] " Laura Abbott
2016-06-08 21:26 ` Kees Cook
2016-06-08 21:26 ` [kernel-hardening] " Kees Cook
2016-06-10 1:14 ` Laura Abbott
2016-06-10 1:14 ` [kernel-hardening] " Laura Abbott
2016-08-01 12:37 ` Linker segfault on powerpc when CONFIG_LKDTM=y (was Re: [kernel-hardening] [PATCH 3/5] lkdtm: add function for testing .rodata section) Michael Ellerman
2016-08-01 12:37 ` [kernel-hardening] " Michael Ellerman
2016-08-01 19:45 ` Kees Cook
2016-08-01 19:45 ` [kernel-hardening] " Kees Cook
2016-08-01 19:45 ` Kees Cook
2016-08-02 3:12 ` [kernel-hardening] " Michael Ellerman
2016-08-02 3:12 ` Michael Ellerman
2016-08-02 3:12 ` Michael Ellerman
2016-08-02 19:12 ` Kees Cook
2016-08-02 19:12 ` Kees Cook
2016-08-03 4:46 ` Michael Ellerman
2016-08-03 4:46 ` Michael Ellerman
2016-08-03 4:46 ` Michael Ellerman
2016-06-07 21:57 ` [PATCH 4/5] lkdtm: add usercopy tests Kees Cook
2016-06-07 21:57 ` [kernel-hardening] " Kees Cook
2016-06-07 23:36 ` kbuild test robot
2016-06-07 23:36 ` [kernel-hardening] " kbuild test robot
2016-06-08 0:07 ` kbuild test robot
2016-06-08 0:07 ` [kernel-hardening] " kbuild test robot
2016-06-07 21:57 ` [PATCH 5/5] lkdtm: split atomic test into over and underflow Kees Cook
2016-06-07 21:57 ` [kernel-hardening] " Kees Cook
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=1465336628-18219-1-git-send-email-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mchehab@osg.samsung.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.