On Mon, May 20, 2019 at 10:37:00AM +0800, Weitao Hou wrote:
> fix lenght to length

What about the other instances of this misspelling? (See "git grep
lenght").

-Kees

> 
> Signed-off-by: Weitao Hou <houweit...@gmail.com>
> ---
> Changes in v2:
>   - fix space before tab warnings
> ---
>  kernel/sysctl.c | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index 943c89178e3d..f78f725f225e 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -187,17 +187,17 @@ extern int no_unaligned_warning;
>   * enum sysctl_writes_mode - supported sysctl write modes
>   *
>   * @SYSCTL_WRITES_LEGACY: each write syscall must fully contain the sysctl 
> value
> - *   to be written, and multiple writes on the same sysctl file descriptor
> - *   will rewrite the sysctl value, regardless of file position. No warning
> - *   is issued when the initial position is not 0.
> + *   to be written, and multiple writes on the same sysctl file descriptor
> + *   will rewrite the sysctl value, regardless of file position. No warning
> + *   is issued when the initial position is not 0.
>   * @SYSCTL_WRITES_WARN: same as above but warn when the initial file 
> position is
> - *   not 0.
> + *   not 0.
>   * @SYSCTL_WRITES_STRICT: writes to numeric sysctl entries must always be at
> - *   file position 0 and the value must be fully contained in the buffer
> - *   sent to the write syscall. If dealing with strings respect the file
> - *   position, but restrict this to the max length of the buffer, anything
> - *   passed the max lenght will be ignored. Multiple writes will append
> - *   to the buffer.
> + *   file position 0 and the value must be fully contained in the buffer
> + *   sent to the write syscall. If dealing with strings respect the file
> + *   position, but restrict this to the max length of the buffer, anything
> + *   passed the max length will be ignored. Multiple writes will append
> + *   to the buffer.
>   *
>   * These write modes control how current file position affects the behavior 
> of
>   * updating sysctl values through the proc interface on each write.
> -- 
> 2.18.0
> 

-- 
Kees Cook

Reply via email to