From: Kees Cook <keescook@chromium.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Lasse Collin <lasse.collin@tukaani.org>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Yinghai Lu <yinghai@kernel.org>,
Baoquan He <bhe@redhat.com>, Borislav Petkov <bp@suse.de>,
"x86@kernel.org" <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH v5 0/2] x86/boot: Warn on future overlapping memcpy() use
Date: Mon, 2 May 2016 15:50:59 -0700 [thread overview]
Message-ID: <1462229461-3370-1-git-send-email-keescook@chromium.org> (raw)
This attempts to bring some sanity to how warn() and error() are defined
so that they can be used by misc.c, kaslr.c, and string.c. After that,
we add a warn() to memcpy and call memmove on detected overlaps.
-Kees
v5:
- split out warn/error into error.c/error.h
v4:
- use __memcpy not memcpy since we've already done the check.
v3:
- call memmove in addition to doing the warning
v2:
- warn about overlapping region
next reply other threads:[~2016-05-02 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 22:50 Kees Cook [this message]
2016-05-02 22:51 ` [PATCH v5 1/2] x86/boot: Extract error reporting functions Kees Cook
2016-05-03 7:45 ` [tip:x86/boot] " tip-bot for Kees Cook
2016-05-02 22:51 ` [PATCH v5 2/2] x86/boot: Warn on future overlapping memcpy() use Kees Cook
2016-05-03 7:46 ` [tip:x86/boot] " tip-bot for 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=1462229461-3370-1-git-send-email-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=bhe@redhat.com \
--cc=bp@suse.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=lasse.collin@tukaani.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@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 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®