[PATCH 15/16] Various source files: spelling fixes on comments
From: Michael Kerrisk (man-pages) <hidden>
Date: 2020-07-16 10:19:37
Subsystem:
the rest · Maintainer:
Linus Torvalds
Signed-off-by: Michael Kerrisk (man-pages) <redacted> --- libcap/cap_proc.c | 6 +++--- libcap/include/uapi/linux/capability.h | 2 +- libcap/include/uapi/linux/securebits.h | 2 +- psx/include/sys/psx_syscall.h | 2 +- psx/psx.c | 6 +++--- 5 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/libcap/cap_proc.c b/libcap/cap_proc.c
index 1c97beb..3929f66 100644
--- a/libcap/cap_proc.c
+++ b/libcap/cap_proc.c@@ -75,7 +75,7 @@ static struct syscaller_s singlethread = { static int _libcap_overrode_syscalls = 1; /* - * psx_load_syscalls() is weakly defined so we can have it overriden + * psx_load_syscalls() is weakly defined so we can have it overridden * by libpsx if that library is linked. Specifically, when libcap * calls psx_load_sycalls() it is prepared to override the default * values for the syscalls that libcap uses to change security state.
@@ -238,7 +238,7 @@ cap_t cap_get_pid(pid_t pid) /* * set the caps on a specific process/pg etc.. The kernel has long - * since deprecated this asynchronus interface. DON'T EXPECT THIS TO + * since deprecated this asynchronous interface. DON'T EXPECT THIS TO * EVER WORK AGAIN. */
@@ -468,7 +468,7 @@ static int _cap_set_mode(struct syscaller_s *sc, cap_mode_t flavor) * set, these modes cannot be undone by the affected process tree and * can only be done by "cap_setpcap" permitted processes. Note, a side * effect of this function, whether it succeeds or fails, is to clear - * atleast the CAP_EFFECTIVE flags for the current process. + * at least the CAP_EFFECTIVE flags for the current process. */ int cap_set_mode(cap_mode_t flavor) {
diff --git a/libcap/include/uapi/linux/capability.h b/libcap/include/uapi/linux/capability.h
index 3281e73..b9ae18b 100644
--- a/libcap/include/uapi/linux/capability.h
+++ b/libcap/include/uapi/linux/capability.h@@ -368,7 +368,7 @@ struct vfs_ns_cap_data { #define CAP_AUDIT_READ 37 -/* Alow system performace and observability privileged opeations using +/* Alow system performance and observability privileged operations using * perf_events, i915_perf and other kernel subsystems. */ #define CAP_PERFMON 38
diff --git a/libcap/include/uapi/linux/securebits.h b/libcap/include/uapi/linux/securebits.h
index 6dae4e9..e9b1309 100644
--- a/libcap/include/uapi/linux/securebits.h
+++ b/libcap/include/uapi/linux/securebits.h@@ -22,7 +22,7 @@ #define SECBIT_NOROOT_LOCKED (issecure_mask(SECURE_NOROOT_LOCKED)) /* When set, setuid to/from uid 0 does not trigger capability-"fixup". - When unset, to provide compatiblility with old programs relying on + When unset, to provide compatibility with old programs relying on set*uid to gain/lose privilege, transitions to/from uid 0 cause capabilities to be gained/lost. */ #define SECURE_NO_SETUID_FIXUP 2
diff --git a/psx/include/sys/psx_syscall.h b/psx/include/sys/psx_syscall.h
index c089a88..8044fbd 100644
--- a/psx/include/sys/psx_syscall.h
+++ b/psx/include/sys/psx_syscall.h@@ -35,7 +35,7 @@ int __real_pthread_create(pthread_t *thread, const pthread_attr_t *attr, /* * psx_syscall performs the specified syscall on all psx registered - * threads. The mecanism by which this occurs is much less efficient + * threads. The mechanism by which this occurs is much less efficient * than a standard system call on Linux, so it should only be used * when POSIX semantics are required to change process relevant * security state.
diff --git a/psx/psx.c b/psx/psx.c
index cabd342..b494072 100644
--- a/psx/psx.c
+++ b/psx/psx.c@@ -29,7 +29,7 @@ #include <sys/syscall.h> /* - * psx_load_syscalls() is weakly defined so we can have it overriden + * psx_load_syscalls() is weakly defined so we can have it overridden * by libpsx if it is linked. Specifically, when libcap calls * psx_load_sycalls it will override their defaut values. As can be * seen here this present function is a no-op. However, if libpsx is
@@ -272,7 +272,7 @@ static void _psx_forked_child(void) { * The only way we can get here is if state is _PSX_INFORK and was * previously _PSX_IDLE. However, none of the registered threads * exist in this newly minted child process, so we have to reset - * the tracking structure to avoid any confusion. We also skuttle + * the tracking structure to avoid any confusion. We also scuttle * any chance of the PSX API working on more than one thread in * the child by leaving the state as _PSX_INFORK. We do support * all psx_syscall()s by reverting to them being direct in the
@@ -343,7 +343,7 @@ static void _psx_exiting(void *node) { } /* - * _psx_start_fn is a trampolene for the intended start function, it + * _psx_start_fn is a trampoline for the intended start function, it * is called blocked (_PSX_CREATE), but releases the block before * calling starter->fn. Before releasing the block, the TLS specific * attributes are initialized for use by the interrupt handler under
--
2.26.2