pstore/ram: Use memcpy_toio instead of memcpy
authorFurquan Shaikh <furquan@google.com>
Mon, 15 Feb 2016 08:19:48 +0000 (09:19 +0100)
committerWilly Tarreau <w@1wt.eu>
Fri, 10 Feb 2017 10:04:01 +0000 (11:04 +0100)
commit0d29b98a434751a1b7c654d4e437883f3f27fe51
tree3f01665468245910febfcfa0e79aac7e85b20847
parent90efe9d4773eedf96d9e4ebb0193da7c6f09ca52
pstore/ram: Use memcpy_toio instead of memcpy

commit 7e75678d23167c2527e655658a8ef36a36c8b4d9 upstream.

persistent_ram_update uses vmap / iomap based on whether the buffer is in
memory region or reserved region. However, both map it as non-cacheable
memory. For armv8 specifically, non-cacheable mapping requests use a
memory type that has to be accessed aligned to the request size. memcpy()
doesn't guarantee that.

Signed-off-by: Furquan Shaikh <furquan@google.com>
Signed-off-by: Enric Balletbo Serra <enric.balletbo@collabora.com>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>
Tested-by: Furquan Shaikh <furquan@chromium.org>
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Willy Tarreau <w@1wt.eu>
fs/pstore/ram_core.c