@@ -123,11 +123,10 @@ static void nfs_readpage_release(struct nfs_page *req, int error)
if (nfs_page_group_sync_on_bit(req, PG_UNLOCKPAGE)) {
struct address_space *mapping = page_file_mapping(page);
- if (PageUptodate(page))
- ; /* FIXME: review fscache page error handling */
- else if (!PageError(page) && !PagePrivate(page))
+ if (!PageUptodate(page) && !PageError(page) && !PagePrivate(page))
generic_error_remove_page(mapping, page);
- if (!nfs_i_fscache(inode))
+ if (!nfs_i_fscache(inode) ||
+ (nfs_i_fscache(inode) && error && !nfs_error_is_fatal_on_server(error)))
unlock_page(page);
}
nfs_release_request(req);
@@ -182,8 +181,9 @@ static void nfs_read_completion(struct nfs_pgio_header *hdr)
nfs_list_remove_request(req);
nfs_readpage_release(req, error);
}
- /* FIXME: NFS_IOHDR_ERROR and NFS_IOHDR_EOF handled per-page */
- nfs_read_completion_to_fscache(hdr, bytes);
+ /* Only call back into fscache if the read was not retried */
+ if (!hdr->error || nfs_error_is_fatal_on_server(hdr->error))
+ nfs_read_completion_to_fscache(hdr, bytes);
out:
hdr->release(hdr);
}
The netfs API handles unlock of pages involved in IOs. However, the current NFS client implementation only utilizes the netfs API when fscache is enabled. If fscache is disabled, NFS is then responsible for unlocking pages involved in READs. This patch addresses an issue when fscache is enabled and READs complete with a retryable error. Specifically this problem is easily reproduced with the connectathon 'holey' test with NFSv2 and a NFS server that does not support READ_PLUS. With such a configuration, the READ_PLUS operation fails with -ENOTSUPP (-524), and due to commit 8f54c7a4babf ("NFS: Fix spurious EIO read errors"), inside nfs_readpage_release() the page is removed from the mapping via generic_error_remove_page(). Since fscache was enabled, nfs_readpage_release() skipped unlocking the page, with the assumption that netfs_subreq_terminated() would unltimately unlock the page inside netfs_rreq_unlock(). However, since NFS removed the page from the mapping, netfs_rreq_unlock() failed to see the page when iterating with xas_for_each, leaving the page locked. Sometime later when the page was freed, a bad page error would result. Fix the above by ensuring NFS unlocks the page and does not call netfs_subreq_terminated() when NFS encounters a retryable error with fscache enabled. Signed-off-by: Dave Wysochanski <dwysocha@redhat.com> --- fs/nfs/read.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)