From: Vasily Gorbik <gor@linux.ibm.com>
To: Kees Cook <keescook@chromium.org>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] s390/speculation: Use statically initialized const for instructions
Date: Tue, 22 Jun 2021 16:16:57 +0200 [thread overview]
Message-ID: <your-ad-here.call-01624371417-ext-0601@work.hours> (raw)
In-Reply-To: <20210616201823.1245603-1-keescook@chromium.org>
On Wed, Jun 16, 2021 at 01:18:23PM -0700, Kees Cook wrote:
> In preparation for FORTIFY_SOURCE performing compile-time and run-time
> field bounds checking for memcpy(), memmove(), and memset(), avoid
> confusing the checks when using a static const source.
>
> Move the static const array into a variable so the compiler can perform
> appropriate bounds checking.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> arch/s390/kernel/nospec-branch.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Applied, thanks!
prev parent reply other threads:[~2021-06-22 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 20:18 [PATCH] s390/speculation: Use statically initialized const for instructions Kees Cook
2021-06-22 14:16 ` Vasily Gorbik [this message]
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=your-ad-here.call-01624371417-ext-0601@work.hours \
--to=gor@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=hca@linux.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.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).