linux-kernel - Re: [PATCH 2/4] nfsd: fix some spelling errors in comments

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: <f27ca56a2b7de7ebb97a4170222047da56eb8eb7.camel@kernel.org>
Date: Fri, 23 Aug 2024 08:07:26 -0400
From: Jeff Layton <jlayton@...nel.org>
To: Li Lingfeng <lilingfeng3@...wei.com>, trondmy@...nel.org,
 anna@...nel.org,  chuck.lever@...cle.com, neilb@...e.de, kolga@...app.com,
 Dai.Ngo@...cle.com,  tom@...pey.com
Cc: linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org, 
	yukuai1@...weicloud.com, houtao1@...wei.com, yi.zhang@...wei.com, 
	yangerkun@...wei.com, lilingfeng@...weicloud.com
Subject: Re: [PATCH 2/4] nfsd: fix some spelling errors in comments

On Fri, 2024-08-23 at 15:00 +0800, Li Lingfeng wrote:
> Fix spelling errors in comments of nfsd4_release_lockowner and
> nfs4_set_delegation.
> 
> Signed-off-by: Li Lingfeng <lilingfeng3@...wei.com>
> ---
>  fs/nfsd/nfs4state.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index a20c2c9d7d45..66a0c76850f3 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -5856,7 +5856,7 @@ nfs4_set_delegation(struct nfsd4_open *open, struct nfs4_ol_stateid *stp,
>  
>  	/*
>  	 * Now that the deleg is set, check again to ensure that nothing
> -	 * raced in and changed the mode while we weren't lookng.
> +	 * raced in and changed the mode while we weren't looking.
>  	 */
>  	status = nfsd4_verify_setuid_write(open, fp->fi_deleg_file);
>  	if (status)
> @@ -8335,7 +8335,7 @@ check_for_locks(struct nfs4_file *fp, struct nfs4_lockowner *lowner)
>   * @cstate: NFSv4 COMPOUND state
>   * @u: RELEASE_LOCKOWNER arguments
>   *
> - * Check if theree are any locks still held and if not - free the lockowner
> + * Check if there are any locks still held and if not - free the lockowner

This is probably better grammatically:

    Check if there are any locks still held and if not, free the lockowner

>   * and any lock state that is owned.
>   *
>   * Return values:

-- 
Jeff Layton <jlayton@...nel.org>