xfs: Rudimentary typo fixes
PATCH 1/1 xfs: Rudimentary typo fixes
s/filesytem/filesystem/
s/instrumention/instrumentation/
Signed-off-by Bhaskar Chowdhury <[email protected]>
--- fs/xfs/xfs_log_recover.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/xfs/xfs_log_recover.c +2 -2
@@ -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
Quoted 5 lines · Bhaskar Chowdhury
s/filesytem/filesystem/
s/instrumention/instrumentation/Signed-off-by Bhaskar Chowdhury <[email protected]>
Looks good to me,
Reviewed-by Darrick J. Wong <[email protected]>
--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@@ -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
Quoted 5 lines · Bhaskar Chowdhury
s/filesytem/filesystem/
s/instrumention/instrumentation/Signed-off-by Bhaskar Chowdhury <[email protected]>
Acked-by Randy Dunlap <[email protected]>
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@@ -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