[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <901034a91a40169ec84f1f699ea86704dff762e4.1593038991.git.luto@kernel.org>
Date: Wed, 24 Jun 2020 15:50:48 -0700
From: Andy Lutomirski <luto@...nel.org>
To: X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Cc: Sasha Levin <sashal@...nel.org>, Andy Lutomirski <luto@...nel.org>
Subject: [PATCH 1/3] selftests/x86/fsgsbase: Fix a comment in the ptrace_write_gsbase test
A comment was unclear. Fix it.
Fixes: 5e7ec8578fa3 ("selftests/x86/fsgsbase: Test ptracer-induced GS base write with FSGSBASE")
Signed-off-by: Andy Lutomirski <luto@...nel.org>
---
tools/testing/selftests/x86/fsgsbase.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/x86/fsgsbase.c b/tools/testing/selftests/x86/fsgsbase.c
index 9a4349813a30..f47495d2f070 100644
--- a/tools/testing/selftests/x86/fsgsbase.c
+++ b/tools/testing/selftests/x86/fsgsbase.c
@@ -498,7 +498,8 @@ static void test_ptrace_write_gsbase(void)
* base would zero the selector. On newer kernels,
* this behavior has changed -- poking the base
* changes only the base and, if FSGSBASE is not
- * available, this may not effect.
+ * available, this may have no effect once the tracee
+ * is resumed.
*/
if (gs == 0)
printf("\tNote: this is expected behavior on older kernels.\n");
--
2.25.4
Powered by blists - more mailing lists