diff options
| author | Nicolas Pitre <[email protected]> | 2020-03-28 21:32:42 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2020-04-23 13:46:31 +0000 |
| commit | 2717769e204e83e65b8819c5e2ef3e5b6639b270 (patch) | |
| tree | 8086e490f73e49d5c5bb5bb82fb4890ce4d48be6 /Documentation/filesystems/caching/cachefiles.rst | |
| parent | tty: serial: owl: add "much needed" clk_prepare_enable() (diff) | |
| download | kernel-2717769e204e83e65b8819c5e2ef3e5b6639b270.tar.gz kernel-2717769e204e83e65b8819c5e2ef3e5b6639b270.zip | |
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 bb1107f7c605 ("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 <[email protected]>
Cc: <[email protected]> # v4.10+
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'Documentation/filesystems/caching/cachefiles.rst')
0 files changed, 0 insertions, 0 deletions