[v6,01/20] mm: fix mapping_set_error call in me_pagecache_dirty

Commit Message

Jeff Layton June 12, 2017, 12:22 p.m. UTC

The error code should be negative. Since this ends up in the default
case anyway, this is harmless, but it's less confusing to negate it.
Also, later patches will require a negative error code here.

Signed-off-by: Jeff Layton <[e-mail]>
Reviewed-by: Ross Zwisler <[e-mail]>
Reviewed-by: Jan Kara <[e-mail]>
Reviewed-by: Matthew Wilcox <[e-mail]>
Reviewed-by: Christoph Hellwig <[e-mail]>
---
 mm/memory-failure.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Patch

diff --git a/mm/memory-failure.c b/mm/memory-failure.c
index 342fac9ba89b..55bc61791fe1 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -684,7 +684,7 @@  static int me_pagecache_dirty(struct page *p, unsigned long pfn)
 		 * the first EIO, but we're not worse than other parts
 		 * of the kernel.
 		 */
-		mapping_set_error(mapping, EIO);
+		mapping_set_error(mapping, -EIO);
 	}
 
 	return me_pagecache_clean(p, pfn);