summaryrefslogtreecommitdiff
path: root/arch/xtensa
diff options
context:
space:
mode:
authorMax Filippov <jcmvbkbc@gmail.com>2017-12-05 08:20:33 +0300
committerMax Filippov <jcmvbkbc@gmail.com>2017-12-17 09:37:13 +0300
commite0baa01438d3fa3979f94f98be19ca3df88e0b7c (patch)
treed9dd381b426ebb1f3a76465099cb5dd2aaca0d29 /arch/xtensa
parentc633544a6154146a210cf158157a1ae7c55473b6 (diff)
downloadlinux-e0baa01438d3fa3979f94f98be19ca3df88e0b7c.tar.xz
xtensa: use __memset in __xtensa_clear_user
memset on xtensa is capable of accessing user memory, but KASAN checks if memset function is actually used for that and reports it as an error: ================================================================== BUG: KASAN: user-memory-access in padzero+0x4d/0x58 Write of size 519 at addr 0049ddf9 by task init/1 Call Trace: [<b0189978>] kasan_report+0x160/0x238 [<b0188818>] check_memory_region+0xf8/0x100 [<b018891c>] memset+0x20/0x34 [<b0238b71>] padzero+0x4d/0x58 ================================================================== Use __memset in __xtensa_clear_user to avoid that. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Diffstat (limited to 'arch/xtensa')
-rw-r--r--arch/xtensa/include/asm/uaccess.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/xtensa/include/asm/uaccess.h b/arch/xtensa/include/asm/uaccess.h
index b8f152b6aaa5..18bbe1caad94 100644
--- a/arch/xtensa/include/asm/uaccess.h
+++ b/arch/xtensa/include/asm/uaccess.h
@@ -261,7 +261,7 @@ raw_copy_to_user(void __user *to, const void *from, unsigned long n)
static inline unsigned long
__xtensa_clear_user(void *addr, unsigned long size)
{
- if ( ! memset(addr, 0, size) )
+ if (!__memset(addr, 0, size))
return size;
return 0;
}