[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1448272404-7031-2-git-send-email-enric.balletbo@collabora.com>
Date: Mon, 23 Nov 2015 10:53:23 +0100
From: Enric Balletbo i Serra <eballetbo@...il.com>
To: linux-kernel@...r.kernel.org
Cc: Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Kees Cook <keescook@...omium.org>,
Tony Luck <tony.luck@...el.com>,
Furquan Shaikh <furquan@...gle.com>,
Aaron Durbin <adurbin@...omium.org>,
Olof Johansson <olofj@...omium.org>,
Andrew Bresticker <abrestic@...omium.org>,
Puneet Kumar <puneetster@...omium.org>,
tomeu.vizoso@...labora.co.uk, gustavo.padovan@...labora.co.uk,
emilio.lopez@...labora.co.uk, sjoerd.simons@...labora.co.uk,
Enric Balletbo Serra <enric.balletbo@...labora.com>
Subject: [PATCH 1/2] fs/pstore: Use memcpy_toio instead of memcpy
From: Furquan Shaikh <furquan@...gle.com>
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@...gle.com>
Reviewed-by: Aaron Durbin <adurbin@...omium.org>
Reviewed-by: Olof Johansson <olofj@...omium.org>
Tested-by: Furquan Shaikh <furquan@...omium.org>
Signed-off-by: Enric Balletbo Serra <enric.balletbo@...labora.com>
---
fs/pstore/ram_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/pstore/ram_core.c b/fs/pstore/ram_core.c
index 76c3f80..351164d 100644
--- a/fs/pstore/ram_core.c
+++ b/fs/pstore/ram_core.c
@@ -299,7 +299,7 @@ static void notrace persistent_ram_update(struct persistent_ram_zone *prz,
const void *s, unsigned int start, unsigned int count)
{
struct persistent_ram_buffer *buffer = prz->buffer;
- memcpy(buffer->data + start, s, count);
+ memcpy_toio(buffer->data + start, s, count);
persistent_ram_update_ecc(prz, start, count);
}
--
2.1.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists