[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20250216160114.83221-1-imvalient@protonmail.com>
Date: Sun, 16 Feb 2025 16:01:49 +0000
From: Imanol <imvalient@...tonmail.com>
To: shuah@...nel.org
Cc: brauner@...nel.org, viro@...iv.linux.org.uk, linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org, Imanol <imvalient@...tonmail.com>
Subject: [PATCH] selftests/core: fix repeated word in close_range_test.c comment
Fixes a minor grammatical issue in a comment in close_range_test.c
where "and and" was mistakenly repeated.
Signed-off-by: Imanol <imvalient@...tonmail.com>
---
tools/testing/selftests/core/close_range_test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/core/close_range_test.c b/tools/testing/selftests/core/close_range_test.c
index e0d9851fe1c9..c19e8d037211 100644
--- a/tools/testing/selftests/core/close_range_test.c
+++ b/tools/testing/selftests/core/close_range_test.c
@@ -506,7 +506,7 @@ TEST(close_range_cloexec_unshare_syzbot)
/*
* Create a huge gap in the fd table. When we now call
- * CLOSE_RANGE_UNSHARE with a shared fd table and and with ~0U as upper
+ * CLOSE_RANGE_UNSHARE with a shared fd table and with ~0U as upper
* bound the kernel will only copy up to fd1 file descriptors into the
* new fd table. If the kernel is buggy and doesn't handle
* CLOSE_RANGE_CLOEXEC correctly it will not have copied all file
--
2.43.0
Powered by blists - more mailing lists