Re: [PATCH v2 1/1] docs: proc.rst: comm: mention the included NUL

[Jonathan Corbet <corbet@lwn.net>]

Christoph Anton Mitterer <mail@christoph.anton.mitterer.name> writes:

> Indicate that the actual value will be one character less.
>
> Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
> ---
>  Documentation/filesystems/proc.rst | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
> index 104c6d047d9b..c0e92a056079 100644
> --- a/Documentation/filesystems/proc.rst
> +++ b/Documentation/filesystems/proc.rst
> @@ -1899,8 +1899,9 @@ For more information on mount propagation see:
>  These files provide a method to access a task's comm value. It also allows for
>  a task to set its own or one of its thread siblings comm value. The comm value
>  is limited in size compared to the cmdline value, so writing anything longer
> -then the kernel's TASK_COMM_LEN (currently 16 chars) will result in a truncated
> -comm value.
> +then the kernel's TASK_COMM_LEN (currently 16 chars, including the null
> +terminator, which is printed as the line feed character in the file) will result
> +in a truncated comm value.

I don't understand the line-feed comment at all; printed by whom?

I think I'll just apply the first version, which explained the situation
well enough.

Thanks,

jon