linux-kernel - Re: [PATCH] English fixes in vmalloced kernel stacks documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b6dd319f-4de7-42e8-a06e-a54633590b29@infradead.org>
Date: Wed, 19 Jun 2024 14:33:53 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Nir Lichtman <nir@...htman.org>, corbet@....net,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] English fixes in vmalloced kernel stacks documentation

Hi,

On 6/19/24 2:07 PM, Nir Lichtman wrote:
> @@ -104,7 +104,7 @@ with PAGE_KERNEL protections.
>  
>  Thread stack allocation is initiated from clone(), fork(), vfork(),
>  kernel_thread() via kernel_clone(). Leaving a few hints for searching
> -the code base to understand when and how thread stack is allocated.
> +the code base to understand when and how a thread stack is allocated.

That last part is still not a sentence AFAICT. How about something like:

>  Thread stack allocation is initiated from clone(), fork(), vfork(),
>  kernel_thread() via kernel_clone(). These are a few hints for searching
>  the code base to understand when and how a thread stack is allocated.

-- 
~Randy