Skip to contentSkip to conversation

xfs: Rudimentary typo fixes

PATCH In review Bhaskar Chowdhury 3 participants 3 messages Mar 20, 2021 XFS filesystem

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 xfs: Rudimentary typo fixes

s/filesytem/filesystem/
s/instrumention/instrumentation/

---
 fs/xfs/xfs_log_recover.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
fs/xfs/xfs_log_recover.c +2 -2
index 97f31308de03..ffa4f6f2f31e 100644
@@ -2736,7 +2736,7 @@ xlog_recover_process_one_iunlink(
  * of log space.
  *
  * This behaviour is bad for latency on single CPU and non-preemptible kernels,
- * and can prevent other filesytem work (such as CIL pushes) from running. This
+ * and can prevent other filesystem work (such as CIL pushes) from running. This
  * can lead to deadlocks if the recovery process runs out of log reservation
  * space. Hence we need to yield the CPU when there is other kernel work
  * scheduled on this CPU to ensure other scheduled work can run without undue
@@ -3404,7 +3404,7 @@ xlog_recover(
 
 		/*
 		 * Delay log recovery if the debug hook is set. This is debug
-		 * instrumention to coordinate simulation of I/O failures with
+		 * instrumentation to coordinate simulation of I/O failures with
 		 * log recovery.
 		 */
 		if (xfs_globals.log_recovery_delay) {

--
2.26.2

Reviewed-by on v1 1/1
#1 lore raw
Quoted 5 lines · Bhaskar Chowdhury

s/filesytem/filesystem/
s/instrumention/instrumentation/

Looks good to me,

--D

Quoted 29 lines
---
 fs/xfs/xfs_log_recover.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
fs/xfs/xfs_log_recover.c +2 -3
index 97f31308de03..ffa4f6f2f31e 100644
@@ -2736,7 +2736,7 @@ xlog_recover_process_one_iunlink(
  * of log space.
  *
  * This behaviour is bad for latency on single CPU and non-preemptible kernels,
- * and can prevent other filesytem work (such as CIL pushes) from running. This
+ * and can prevent other filesystem work (such as CIL pushes) from running. This
  * can lead to deadlocks if the recovery process runs out of log reservation
  * space. Hence we need to yield the CPU when there is other kernel work
  * scheduled on this CPU to ensure other scheduled work can run without undue
@@ -3404,7 +3404,7 @@ xlog_recover(
 
 		/*
 		 * Delay log recovery if the debug hook is set. This is debug
-		 * instrumention to coordinate simulation of I/O failures with
+		 * instrumentation to coordinate simulation of I/O failures with
 		 * log recovery.
 		 */
 		if (xfs_globals.log_recovery_delay) {
--

2.26.2

Acked-by on v1 1/1
#2 lore raw
In reply to Bhaskar Chowdhury
Quoted 5 lines · Bhaskar Chowdhury

s/filesytem/filesystem/
s/instrumention/instrumentation/

Quoted 30 lines

---
fs/xfs/xfs_log_recover.c | 4 ++--

1 file changed, 2 insertions(+), 2 deletions(-)
fs/xfs/xfs_log_recover.c +2 -3
index 97f31308de03..ffa4f6f2f31e 100644
@@ -2736,7 +2736,7 @@ xlog_recover_process_one_iunlink(
 * of log space.
 *
 * This behaviour is bad for latency on single CPU and non-preemptible kernels,
- * and can prevent other filesytem work (such as CIL pushes) from running. This
+ * and can prevent other filesystem work (such as CIL pushes) from running. This
 * can lead to deadlocks if the recovery process runs out of log reservation
 * space. Hence we need to yield the CPU when there is other kernel work
 * scheduled on this CPU to ensure other scheduled work can run without undue
@@ -3404,7 +3404,7 @@ xlog_recover(
 
 		/*
 		 * Delay log recovery if the debug hook is set. This is debug
-		 * instrumention to coordinate simulation of I/O failures with
+		 * instrumentation to coordinate simulation of I/O failures with
 		 * log recovery.
 		 */
 		if (xfs_globals.log_recovery_delay) {
--

2.26.2