From: Jean Delvare <jdelvare@suse.de>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Fix English in description of GCC_PLUGIN_STRUCTLEAK
Date: Mon, 24 Apr 2017 08:52:37 +0200 [thread overview]
Message-ID: <20170424085237.7c561c06@endymion> (raw)
Signed-off-by: Jean Delvare <jdelvare@suse.de>
Fixes: c61f13eaa1ee ("gcc-plugins: Add structleak for more stack initialization")
Cc: Kees Cook <keescook@chromium.org>
---
arch/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-4.11-rc8.orig/arch/Kconfig 2017-04-03 02:23:54.000000000 +0200
+++ linux-4.11-rc8/arch/Kconfig 2017-04-24 08:42:42.889766657 +0200
@@ -418,7 +418,7 @@ config GCC_PLUGIN_STRUCTLEAK
bool "Force initialization of variables containing userspace addresses"
depends on GCC_PLUGINS
help
- This plugin zero-initializes any structures that containing a
+ This plugin zero-initializes any structures containing a
__user attribute. This can prevent some classes of information
exposures.
--
Jean Delvare
SUSE L3 Support
next reply other threads:[~2017-04-24 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 6:52 Jean Delvare [this message]
2017-04-24 20:41 ` Fix English in description of GCC_PLUGIN_STRUCTLEAK 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=20170424085237.7c561c06@endymion \
--to=jdelvare@suse.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
/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.