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]
Date:   Tue, 16 Mar 2021 22:15:35 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Bhaskar Chowdhury <unixbhaskar@...il.com>,
        akpm@...ux-foundation.org, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: Typo fix in the file util.c

On 3/16/21 8:34 PM, Bhaskar Chowdhury wrote:
> 
> 
> s/condtion/condition/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>

Acked-by: Randy Dunlap <rdunlap@...radead.org>

> ---
>  mm/util.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/mm/util.c b/mm/util.c
> index 54870226cea6..f85da35b50eb 100644
> --- a/mm/util.c
> +++ b/mm/util.c
> @@ -775,7 +775,7 @@ int overcommit_policy_handler(struct ctl_table *table, int write, void *buffer,
>  	 * The deviation of sync_overcommit_as could be big with loose policy
>  	 * like OVERCOMMIT_ALWAYS/OVERCOMMIT_GUESS. When changing policy to
>  	 * strict OVERCOMMIT_NEVER, we need to reduce the deviation to comply
> -	 * with the strict "NEVER", and to avoid possible race condtion (even
> +	 * with the strict "NEVER", and to avoid possible race condition (even
>  	 * though user usually won't too frequently do the switching to policy
>  	 * OVERCOMMIT_NEVER), the switch is done in the following order:
>  	 *	1. changing the batch
> --


-- 
~Randy

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ