linux-kernel - [PATCH] kselftest/pidfd: Fix typos 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>] [day] [month] [year] [list]

Message-ID: <20250521050751.629473-1-ipravdin.official@gmail.com>
Date: Wed, 21 May 2025 01:07:50 -0400
From: Ivan Pravdin <ipravdin.official@...il.com>
To: brauner@...nel.org,
	shuah@...nel.org
Cc: linux-kernel@...r.kernel.org,
	linux-kselftest@...r.kernel.org,
	Ivan Pravdin <ipravdin.official@...il.com>
Subject: [PATCH] kselftest/pidfd: Fix typos in comments

Fix typos in comments in pidfd_info_test.c

Signed-off-by: Ivan Pravdin <ipravdin.official@...il.com>
---
 tools/testing/selftests/pidfd/pidfd_info_test.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tools/testing/selftests/pidfd/pidfd_info_test.c b/tools/testing/selftests/pidfd/pidfd_info_test.c
index 1758a1b0457b..53cb429f5fa0 100644
--- a/tools/testing/selftests/pidfd/pidfd_info_test.c
+++ b/tools/testing/selftests/pidfd/pidfd_info_test.c
@@ -229,7 +229,7 @@ static void *pidfd_info_pause_thread(void *arg)
 
 	close(ipc_socket);
 
-	/* Sleep untill we're killed. */
+	/* Sleep until we're killed. */
 	pause();
 	return NULL;
 }
@@ -518,7 +518,7 @@ TEST_F(pidfd_info, thread_group_exec)
 	EXPECT_EQ(sys_pidfd_send_signal(pidfd_leader, SIGKILL, NULL, 0), 0);
 
 	/*
-	 * Afte the exec we're dealing with an empty thread-group so now
+	 * After the exec we're dealing with an empty thread-group so now
 	 * we must see an exit notification on the thread-specific pidfd
 	 * for the thread-group leader as there's no subthread that can
 	 * revive the struct pid.
@@ -665,7 +665,7 @@ TEST_F(pidfd_info, thread_group_exec_thread)
 	EXPECT_EQ(sys_pidfd_send_signal(pidfd_leader, SIGKILL, NULL, 0), 0);
 
 	/*
-	 * Afte the exec we're dealing with an empty thread-group so now
+	 * After the exec we're dealing with an empty thread-group so now
 	 * we must see an exit notification on the thread-specific pidfd
 	 * for the thread-group leader as there's no subthread that can
 	 * revive the struct pid.
-- 
2.45.2