[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170308162934.21989-2-jlayton@redhat.com>
Date: Wed, 8 Mar 2017 11:29:26 -0500
From: Jeff Layton <jlayton@...hat.com>
To: viro@...iv.linux.org.uk, akpm@...ux-foundation.org
Cc: konishi.ryusuke@....ntt.co.jp, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-nilfs@...r.kernel.org, ross.zwisler@...ux.intel.com,
jack@...e.cz, neilb@...e.com, openosd@...il.com, adilger@...ger.ca,
James.Bottomley@...senPartnership.com
Subject: [PATCH v2 1/9] mm: fix mapping_set_error call in me_pagecache_dirty
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.
Signed-off-by: Jeff Layton <jlayton@...hat.com>
---
mm/memory-failure.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memory-failure.c b/mm/memory-failure.c
index 27f7210e7fab..4b56e53e5378 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -674,7 +674,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);
--
2.9.3
Powered by blists - more mailing lists