From: Brad Spengler <spender@grsecurity.net>
To: Kees Cook <keescook@chromium.org>
Cc: kernel-hardening@lists.openwall.com,
PaX Team <pageexec@freemail.hu>,
Casey Schaufler <casey.schaufler@intel.com>,
Rik van Riel <riel@redhat.com>, Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [kernel-hardening] Re: [PATCH v2 1/4] mm: Hardened usercopy
Date: Wed, 8 Jun 2016 20:47:58 -0400 [thread overview]
Message-ID: <20160609004758.GA8658@grsecurity.net> (raw)
In-Reply-To: <1465420302-23754-2-git-send-email-keescook@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
> diff --git a/mm/usercopy.c b/mm/usercopy.c
> new file mode 100644
> index 000000000000..e09c33070759
> --- /dev/null
> +++ b/mm/usercopy.c
> @@ -0,0 +1,177 @@
> +/*
> + * This implements the various checks for CONFIG_HARDENED_USERCOPY*,
> + * which are designed to protect kernel memory from needless exposure
> + * and overwrite under many conditions.
> + */
As this is a new file being introduced which is (modulo some bikeshedding
and addition of a few comments) a direct copy+paste of our code and comments
in fs/exec.c, I would appreciate both a GPL notice (the same as exists for
KASAN, etc) and both the PaX Team and myself being listed as the copyright
owners.
-Brad
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-06-09 0:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 21:11 [kernel-hardening] [RFC][PATCH v2 0/4] mm: Hardened usercopy Kees Cook
2016-06-08 21:11 ` [kernel-hardening] [PATCH v2 1/4] " Kees Cook
2016-06-09 0:47 ` Brad Spengler [this message]
2016-06-09 1:39 ` [kernel-hardening] " Rik van Riel
2016-06-09 2:58 ` Kees Cook
2016-07-12 23:04 ` Kees Cook
2016-06-08 21:11 ` [kernel-hardening] [PATCH v2 2/4] usercopy: avoid direct copying to userspace Kees Cook
2016-06-09 23:37 ` [kernel-hardening] " Rik van Riel
2016-06-10 21:09 ` Kees Cook
2016-06-11 1:08 ` Rik van Riel
2016-06-08 21:11 ` [kernel-hardening] [PATCH v2 3/4] usercopy: whitelist user-copyable caches Kees Cook
2016-06-08 21:11 ` [kernel-hardening] [PATCH v2 4/4] usercopy: provide split of user-controlled slabs Kees Cook
2016-06-09 3:02 ` [kernel-hardening] [RFC][PATCH v2 5/4] arm: fixes for usercopy Kees Cook
2016-06-09 15:35 ` [kernel-hardening] RE: [RFC][PATCH v2 0/4] mm: Hardened usercopy Schaufler, Casey
2016-06-09 17:48 ` [kernel-hardening] " Kees Cook
2016-06-09 23:39 ` [kernel-hardening] [RFC][PATCH 6/4] mm: disallow user copy to/from separately allocated pages Rik van Riel
2016-06-10 19:44 ` [kernel-hardening] [RFC][PATCH v2 " Rik van Riel
2016-06-10 20:46 ` [kernel-hardening] " Kees Cook
2016-06-24 20:53 ` Kees Cook
2016-06-24 20:57 ` Rik van Riel
2016-06-24 20:59 ` Kees Cook
2016-06-16 1:30 ` [kernel-hardening] [RFC][PATCH v2 0/4] mm: Hardened usercopy Valdis.Kletnieks
2016-06-16 1:38 ` Kees Cook
2016-06-16 23:36 ` Valdis.Kletnieks
2016-06-17 1:38 ` Valdis.Kletnieks
2016-06-18 19:30 ` 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=20160609004758.GA8658@grsecurity.net \
--to=spender@grsecurity.net \
--cc=akpm@linux-foundation.org \
--cc=casey.schaufler@intel.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=pageexec@freemail.hu \
--cc=penberg@kernel.org \
--cc=riel@redhat.com \
--cc=rientjes@google.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).