Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
Documentation: English corrections in vmalloced kernel stacks
Minor grammar fixes in vmalloced-kernel-stacks
Signed-off-by: Nir Lichtman <nir@lichtman.org>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20240619215944.GA3571421@lichtman.org
authored by
Nir Lichtman
and committed by
Jonathan Corbet
27a0781a
ddb77059
+5
-5
+5
-5
Documentation/mm/vmalloced-kernel-stacks.rst
+5
-5
Documentation/mm/vmalloced-kernel-stacks.rst
···
22
22
susceptible to exploits. Problems could show up at a later time making
23
23
it difficult to isolate and root-cause.
24
24
25
-
Virtually-mapped kernel stacks with guard pages causes kernel stack
25
+
Virtually mapped kernel stacks with guard pages cause kernel stack
26
26
overflows to be caught immediately rather than causing difficult to
27
27
diagnose corruptions.
28
28
···
57
57
VMAP_STACK
58
58
----------
59
59
60
-
VMAP_STACK bool configuration option when enabled allocates virtually
60
+
When enabled, the VMAP_STACK bool configuration option allocates virtually
61
61
mapped task stacks. This option depends on HAVE_ARCH_VMAP_STACK.
62
62
63
63
- Enable this if you want the use virtually-mapped kernel stacks
···
83
83
Allocation
84
84
-----------
85
85
86
-
When a new kernel thread is created, thread stack is allocated from
86
+
When a new kernel thread is created, a thread stack is allocated from
87
87
virtually contiguous memory pages from the page level allocator. These
88
88
pages are mapped into contiguous kernel virtual space with PAGE_KERNEL
89
89
protections.
···
103
103
- This does not address interrupt stacks - according to the original patch
104
104
105
105
Thread stack allocation is initiated from clone(), fork(), vfork(),
106
-
kernel_thread() via kernel_clone(). Leaving a few hints for searching
107
-
the code base to understand when and how thread stack is allocated.
106
+
kernel_thread() via kernel_clone(). These are a few hints for searching
107
+
the code base to understand when and how a thread stack is allocated.
108
108
109
109
Bulk of the code is in:
110
110
`kernel/fork.c <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/fork.c>`.