linux-kernel - Re: [PATCH V2] locking: Fix a typo of comment

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] [day] [month] [year] [list]

Message-ID: <628d3801-0a9e-c25b-c509-6db98a8afc14@infradead.org>
Date:   Mon, 8 May 2023 19:32:34 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Wang Honghui <honghui.wang@...s.com.cn>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
        Waiman Long <longman@...hat.com>,
        Boqun Feng <boqun.feng@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] locking: Fix a typo of comment



On 5/8/23 19:24, Wang Honghui wrote:
> 
> As title
> 
> Signed-off-by: Wang Honghui <honghui.wang@...s.com.cn>
> ---
>  kernel/locking/mutex.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
> index d973fe6041bf..fe7335fb63d4 100644
> --- a/kernel/locking/mutex.c
> +++ b/kernel/locking/mutex.c
> @@ -362,7 +362,7 @@ bool mutex_spin_on_owner(struct mutex *lock, struct task_struct *owner,
>  		 * checking lock->owner still matches owner. And we already
>  		 * disabled preemption which is equal to the RCU read-side
>  		 * crital section in optimistic spinning code. Thus the

		   critical

> -		 * task_strcut structure won't go away during the spinning
> +		 * task_struct structure won't go away during the spinning
>  		 * period

		   period.

>  		 */
>  		barrier();
> @@ -401,7 +401,7 @@ static inline int mutex_can_spin_on_owner(struct mutex *lock)
>  
>  	/*
>  	 * We already disabled preemption which is equal to the RCU read-side
> -	 * crital section in optimistic spinning code. Thus the task_strcut
> +	 * crital section in optimistic spinning code. Thus the task_struct

	   critical

>  	 * structure won't go away during the spinning period.
>  	 */
>  	owner = __mutex_owner(lock);

-- 
~Randy