selftests/memfd: fix spelling mistakes
authorSaurav Shah <sauravshah.31@gmail.com>
Wed, 1 May 2024 23:13:17 +0000 (04:43 +0530)
committerAndrew Morton <akpm@linux-foundation.org>
Tue, 7 May 2024 17:36:59 +0000 (10:36 -0700)
Fix spelling mistakes in the comments.

Link: https://lkml.kernel.org/r/20240501231317.24648-1-sauravshah.31@gmail.com
Signed-off-by: Saurav Shah <sauravshah.31@gmail.com>
Cc: Aleksa Sarai <cyphar@cyphar.com>
Cc: Greg Thelen <gthelen@google.com>
Cc: Jeff Xu <jeffxu@google.com>
Cc: Shuah Khan <shuah@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
tools/testing/selftests/memfd/fuse_test.c
tools/testing/selftests/memfd/memfd_test.c

index 93798c8c5d54b5760d353645da5047c18ea1ca21..dbc171a3806db51de79e100970ae1f4733acc72d 100644 (file)
@@ -306,7 +306,7 @@ int main(int argc, char **argv)
         * then the kernel did a page-replacement or canceled the read() (or
         * whatever magic it did..). In that case, the memfd object is still
         * all zero.
-        * In case the memfd-object was *not* sealed, the read() was successfull
+        * In case the memfd-object was *not* sealed, the read() was successful
         * and the memfd object must *not* be all zero.
         * Note that in real scenarios, there might be a mixture of both, but
         * in this test-cases, we have explicit 200ms delays which should be
index 18f585684e20253b19e4e7eee60cc5505f99f05f..95af2d78fd318ce1e76334ddc7afb4e6e46dc45d 100644 (file)
@@ -1528,7 +1528,7 @@ static void test_share_open(char *banner, char *b_suffix)
 
 /*
  * Test sharing via fork()
- * Test whether seal-modifications work as expected with forked childs.
+ * Test whether seal-modifications work as expected with forked children.
  */
 static void test_share_fork(char *banner, char *b_suffix)
 {