linux-kernel - Re: [PATCH] dlm: fix a typo

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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 22 Jul 2019 08:55:11 +0200
From:   "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To:     Christophe JAILLET <christophe.jaillet@...adoo.fr>,
        ccaulfie@...hat.com, teigland@...hat.com
Cc:     cluster-devel@...hat.com, linux-kernel@...r.kernel.org,
        kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] dlm: fix a typo

On 21.07.19 12:43, Christophe JAILLET wrote:
> s/locksapce/lockspace
> 
> Signed-off-by: Christophe JAILLET <christophe.jaillet@...adoo.fr>
> ---
>   fs/dlm/lockspace.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/dlm/lockspace.c b/fs/dlm/lockspace.c
> index 00fa700f4e83..9c95df8a36e9 100644
> --- a/fs/dlm/lockspace.c
> +++ b/fs/dlm/lockspace.c
> @@ -870,7 +870,7 @@ static int release_lockspace(struct dlm_ls *ls, int force)
>    * until this returns.
>    *
>    * Force has 4 possible values:
> - * 0 - don't destroy locksapce if it has any LKBs
> + * 0 - don't destroy lockspace if it has any LKBs
>    * 1 - destroy lockspace if it has remote LKBs but not if it has local LKBs
>    * 2 - destroy lockspace regardless of LKBs
>    * 3 - destroy lockspace as part of a forced shutdown
> 

Reviewed-By: Enrico Weigelt <info@...ux.net>


-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@...ux.net -- +49-151-27565287