Max Filippov e0baa01438 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>		2017-12-16 22:37:13 -08:00
..
boot	xtensa: add support for KASAN	2017-12-16 22:37:12 -08:00
configs	xtensa: add default memmap and mmio32native options to defconfigs	2016-09-20 20:43:24 -07:00
include	xtensa: use __memset in __xtensa_clear_user	2017-12-16 22:37:13 -08:00
kernel	xtensa: add support for KASAN	2017-12-16 22:37:12 -08:00
lib	xtensa: add support for KASAN	2017-12-16 22:37:12 -08:00
mm	xtensa: add support for KASAN	2017-12-16 22:37:12 -08:00
oprofile	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
platforms	xtensa: clean up custom-controlled debug output	2017-12-16 22:37:08 -08:00
variants	xtensa: Added Cadence CSP kernel configuration for Xtensa	2016-09-09 18:39:09 -07:00
Kconfig	xtensa: add support for KASAN	2017-12-16 22:37:12 -08:00
Kconfig.debug	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
Makefile	xtensa: build kernel with text-section-literals	2017-12-10 14:48:51 -08:00