summaryrefslogtreecommitdiffstats
path: root/drivers/pcmcia/Kconfig
diff options
context:
space:
mode:
authorAndrew Jeffery <andrew@aj.id.au>2023-02-22 00:10:14 +0100
committerRussell King (Oracle) <rmk+kernel@armlinux.org.uk>2023-03-06 16:25:08 +0100
commitceac10c83b330680cc01ceaaab86cd49f4f30d81 (patch)
tree143774c2573b877327e1bcd8dedb924a9e2f67fa /drivers/pcmcia/Kconfig
parentLinux 6.2 (diff)
downloadlinux-ceac10c83b330680cc01ceaaab86cd49f4f30d81.tar.xz
linux-ceac10c83b330680cc01ceaaab86cd49f4f30d81.zip
ARM: 9290/1: uaccess: Fix KASAN false-positives
__copy_to_user_memcpy() and __clear_user_memset() had been calling memcpy() and memset() respectively, leading to false-positive KASAN reports when starting userspace: [ 10.707901] Run /init as init process [ 10.731892] process '/bin/busybox' started with executable stack [ 10.745234] ================================================================== [ 10.745796] BUG: KASAN: user-memory-access in __clear_user_memset+0x258/0x3ac [ 10.747260] Write of size 2687 at addr 000de581 by task init/1 Use __memcpy() and __memset() instead to allow userspace access, which is of course the intent of these functions. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Reviewed-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Diffstat (limited to 'drivers/pcmcia/Kconfig')
0 files changed, 0 insertions, 0 deletions