Fix typos in module/

Reviewed-by: Ryan Moeller <[email protected]>
Reviewed-by: Richard Laager <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Andrea Gelmini <[email protected]>
Closes #9241 

4 files changed, 8 insertions, 8 deletions

diff --git a/module/spl/spl-condvar.c b/module/spl/spl-condvar.c
index 664fae1e7..3cc33da62 100644
--- a/module/spl/spl-condvar.c
+++ b/module/spl/spl-condvar.c
@@ -431,8 +431,8 @@ __cv_signal(kcondvar_t *cvp)
 
 	/*
 	 * All waiters are added with WQ_FLAG_EXCLUSIVE so only one
-	 * waiter will be set runable with each call to wake_up().
-	 * Additionally wake_up() holds a spin_lock assoicated with
+	 * waiter will be set runnable with each call to wake_up().
+	 * Additionally wake_up() holds a spin_lock associated with
 	 * the wait queue to ensure we don't race waking up processes.
 	 */
 	if (atomic_read(&cvp->cv_waiters) > 0)
diff --git a/module/spl/spl-generic.c b/module/spl/spl-generic.c
index 3c5ef60bd..1deb2f444 100644
--- a/module/spl/spl-generic.c
+++ b/module/spl/spl-generic.c
@@ -79,7 +79,7 @@ EXPORT_SYMBOL(p0);
  * to generate words larger than 128 bits will paradoxically be limited to
  * `2^128 - 1` possibilities. This is because we have a sequence of `2^128 - 1`
  * 128-bit words and selecting the first will implicitly select the second. If
- * a caller finds this behavior undesireable, random_get_bytes() should be used
+ * a caller finds this behavior undesirable, random_get_bytes() should be used
  * instead.
  *
  * XXX: Linux interrupt handlers that trigger within the critical section
@@ -207,7 +207,7 @@ nlz64(uint64_t x)
 
 /*
  * Newer kernels have a div_u64() function but we define our own
- * to simplify portibility between kernel versions.
+ * to simplify portability between kernel versions.
  */
 static inline uint64_t
 __div_u64(uint64_t u, uint32_t v)
diff --git a/module/spl/spl-kmem-cache.c b/module/spl/spl-kmem-cache.c
index 44e112ccc..b39867b03 100644
--- a/module/spl/spl-kmem-cache.c
+++ b/module/spl/spl-kmem-cache.c
@@ -185,7 +185,7 @@ MODULE_PARM_DESC(spl_kmem_cache_kmem_threads,
 
 struct list_head spl_kmem_cache_list;   /* List of caches */
 struct rw_semaphore spl_kmem_cache_sem; /* Cache list lock */
-taskq_t *spl_kmem_cache_taskq;		/* Task queue for ageing / reclaim */
+taskq_t *spl_kmem_cache_taskq;		/* Task queue for aging / reclaim */
 
 static void spl_cache_shrink(spl_kmem_cache_t *skc, void *obj);
 
@@ -995,7 +995,7 @@ spl_kmem_cache_create(char *name, size_t size, size_t align,
 #if defined(SLAB_USERCOPY)
 		/*
 		 * Required for PAX-enabled kernels if the slab is to be
-		 * used for coping between user and kernel space.
+		 * used for copying between user and kernel space.
 		 */
 		slabflags |= SLAB_USERCOPY;
 #endif
diff --git a/module/spl/spl-tsd.c b/module/spl/spl-tsd.c
index 4c800292a..14342d5a6 100644
--- a/module/spl/spl-tsd.c
+++ b/module/spl/spl-tsd.c
@@ -42,7 +42,7 @@
  *  type is entry is called a 'key' entry and it is added to the hash during
  *  tsd_create().  It is used to store the address of the destructor function
  *  and it is used as an anchor point.  All tsd entries which use the same
- *  key will be linked to this entry.  This is used during tsd_destory() to
+ *  key will be linked to this entry.  This is used during tsd_destroy() to
  *  quickly call the destructor function for all tsd associated with the key.
  *  The 'key' entry may be looked up with tsd_hash_search() by passing the
  *  key you wish to lookup and DTOR_PID constant as the pid.
@@ -269,7 +269,7 @@ tsd_hash_add_key(tsd_hash_table_t *table, uint_t *keyp, dtor_func_t dtor)
  * @table: hash table
  * @pid: search pid
  *
- * For every process these is a single entry in the hash which is used
+ * For every process there is a single entry in the hash which is used
  * as anchor.  All other thread specific entries for this process are
  * linked to this anchor via the 'he_pid_list' list head.
  */