[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170308162934.21989-8-jlayton@redhat.com>
Date: Wed, 8 Mar 2017 11:29:32 -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 7/9] mm: ensure that we set mapping error if writeout() fails
If writepage fails during a page migration, then we need to ensure that
fsync will see it by flagging the mapping.
Signed-off-by: Jeff Layton <jlayton@...hat.com>
---
mm/migrate.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/mm/migrate.c b/mm/migrate.c
index 9a0897a14d37..a9c0b46865b7 100644
--- a/mm/migrate.c
+++ b/mm/migrate.c
@@ -789,7 +789,11 @@ static int writeout(struct address_space *mapping, struct page *page)
/* unlocked. Relock */
lock_page(page);
- return (rc < 0) ? -EIO : -EAGAIN;
+ if (rc < 0) {
+ mapping_set_error(mapping, rc);
+ return -EIO;
+ }
+ return -EAGAIN;
}
/*
--
2.9.3
Powered by blists - more mailing lists