mm, oom: do not schedule if current has been killed

[~andy/linux] / mm / page-writeback.c

diff --git a/mm/page-writeback.c b/mm/page-writeback.c
index ec14419e53b5c2408fe50bea7ac11a0b21c912f2..e5363f34e0250656c357d965a2e8949577cfb607 100644 (file)
--- a/mm/page-writeback.c
+++ b/mm/page-writeback.c
@@ -946,7 +946,7 @@ static void bdi_update_dirty_ratelimit(struct backing_dev_info *bdi,
         *      bdi->dirty_ratelimit = balanced_dirty_ratelimit;
         *
         * However to get a more stable dirty_ratelimit, the below elaborated
-        * code makes use of task_ratelimit to filter out sigular points and
+        * code makes use of task_ratelimit to filter out singular points and
         * limit the step size.
         *
         * The below code essentially only uses the relative value of
@@ -969,7 +969,7 @@ static void bdi_update_dirty_ratelimit(struct backing_dev_info *bdi,
         * feel and care are stable dirty rate and small position error.
         *
         * |task_ratelimit - dirty_ratelimit| is used to limit the step size
-        * and filter out the sigular points of balanced_dirty_ratelimit. Which
+        * and filter out the singular points of balanced_dirty_ratelimit. Which
         * keeps jumping around randomly and can even leap far away at times
         * due to the small 200ms estimation period of dirty_rate (we want to
         * keep that period small to reduce time lags).