linux-kernel - Re: [PATCH] Fix typo in kernel/futex.c, "even though" instead of "even through"

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

Date:   Tue, 27 Apr 2021 13:35:14 -0400
From:   bilbao@...edu
To:     tglx@...utronix.de, mingo@...hat.com, peterz@...radead.org,
        dvhart@...radead.org, linux-kernel@...r.kernel.org,
        Carlos Bilbao <bilbao@...edu>
Subject: Re: [PATCH] Fix typo in kernel/futex.c, "even though" instead of "even  through"

Hello, I attach changelog and the patch as plain text here.

This patch fixes a typo in a comment of kernel/futex.c, changing 'even through' for 'even though'.

Signed-off-by: Carlos Bilbao <bilbao@...edu>
---
 kernel/futex.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/futex.c b/kernel/futex.c
index 00febd6dea9c..f8035bb11265 100644
--- a/kernel/futex.c
+++ b/kernel/futex.c
@@ -2851,7 +2851,7 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned int flags,
 	/*
 	 * On PREEMPT_RT_FULL, when hb->lock becomes an rt_mutex, we must not
 	 * hold it while doing rt_mutex_start_proxy(), because then it will
-	 * include hb->lock in the blocking chain, even through we'll not in
+	 * include hb->lock in the blocking chain, even though we'll not in
 	 * fact hold it while blocking. This will lead it to report -EDEADLK
 	 * and BUG when futex_unlock_pi() interleaves with this.
 	 *
-- 
2.25.1

On Monday, April 26, 2021 5:11:38 PM EDT Carlos Bilbao wrote:
> Signed-off-by: Carlos Bilbao <bilbao@...edu>
> ---
>  kernel/futex.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/futex.c b/kernel/futex.c
> index 00febd6dea9c..f8035bb11265 100644
> --- a/kernel/futex.c
> +++ b/kernel/futex.c
> @@ -2851,7 +2851,7 @@ static int futex_lock_pi(u32 __user *uaddr, unsigned
> int flags,
>   /*
>   * On PREEMPT_RT_FULL, when hb->lock becomes an rt_mutex, we must not
>   * hold it while doing rt_mutex_start_proxy(), because then it will
> - * include hb->lock in the blocking chain, even through we'll not in
> + * include hb->lock in the blocking chain, even though we'll not in
>   * fact hold it while blocking. This will lead it to report -EDEADLK
>   * and BUG when futex_unlock_pi() interleaves with this.
>   *