[PATCH v5 0/2] x86/boot: Warn on future overlapping memcpy() use

From	Kees Cook <keescook@chromium.org>
Newsgroups	linux.kernel
Subject	[PATCH v5 0/2] x86/boot: Warn on future overlapping memcpy() use
Date	2016-05-03 01:00 +0200
Message-ID	<ruuYN-46k-1@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View 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

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

[PATCH v5 0/2] x86/boot: Warn on future overlapping memcpy() use Kees Cook <keescook@chromium.org> - 2016-05-03 01:00 +0200
  [PATCH v5 2/2] x86/boot: Warn on future overlapping memcpy() use Kees Cook <keescook@chromium.org> - 2016-05-03 01:00 +0200
    [tip:x86/boot] x86/boot: Warn on future overlapping memcpy() use tip-bot for Kees Cook <tipbot@zytor.com> - 2016-05-03 09:50 +0200
  [PATCH v5 1/2] x86/boot: Extract error reporting functions Kees Cook <keescook@chromium.org> - 2016-05-03 01:00 +0200
    [tip:x86/boot] x86/boot: Extract error reporting functions tip-bot for Kees Cook <tipbot@zytor.com> - 2016-05-03 09:50 +0200

csiph-web