Nicolas Pitre 2717769e20 vt: don't hardcode the mem allocation upper bound ... The code in vc_do_resize() bounds the memory allocation size to avoid exceeding MAX_ORDER down the kzalloc() call chain and generating a runtime warning triggerable from user space. However, not only is it unwise to use a literal value here, but MAX_ORDER may also be configurable based on CONFIG_FORCE_MAX_ZONEORDER. Let's use KMALLOC_MAX_SIZE instead. Note that prior commit bb1107f7c6 ("mm, slab: make sure that KMALLOC_MAX_SIZE will fit into MAX_ORDER") the KMALLOC_MAX_SIZE value could not be relied upon. Signed-off-by: Nicolas Pitre <nico@fluxnic.net> Cc: <stable@vger.kernel.org> # v4.10+ Link: https://lore.kernel.org/r/nycvar.YSQ.7.76.2003281702410.2671@knanqh.ubzr Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2020-04-23 15:46:31 +02:00
..
.gitignore	tty: vt: move conmakehash to drivers/tty/vt/ from scripts/	2019-12-17 14:42:46 +01:00
conmakehash.c	tty: vt: move conmakehash to drivers/tty/vt/ from scripts/	2019-12-17 14:42:46 +01:00
consolemap.c
cp437.uni
defkeymap.c_shipped
defkeymap.map
keyboard.c	tty: vt: keyboard: reject invalid keycodes	2019-11-23 18:31:07 +01:00
Makefile	kbuild: rename hostprogs-y/always to hostprogs/always-y	2020-02-04 01:53:07 +09:00
selection.c	vt: selection, use rounddown() for start/endline computation	2020-03-16 08:41:17 +01:00
vc_screen.c	vcs: prevent write access to vcsu devices	2019-11-27 07:47:17 +01:00
vt.c	vt: don't hardcode the mem allocation upper bound	2020-04-23 15:46:31 +02:00
vt_ioctl.c	vt: vt_ioctl: fix use-after-free in vt_in_use()	2020-03-27 12:35:04 +01:00