Recent changes to close can delay pending layoutcommit until umount,
when the async layoutcommits can come tricklng in after we have destroyed
the session. Since file does not need them, just turn them off for
the moment. Non-file layouts will probably have to trigger them in
some fashion at close.
A better solution is to just push all the layoutcommit code outside
of the pnfs-submit branch. This is really just a stop gap until code
is rearranged to make that easier.
Signed-off-by: Fred Isaman <iisaman@xxxxxxxxxx>
---
fs/nfs/nfs4proc.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 9b15535..224bdfe 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -3098,7 +3098,6 @@ static void pnfs4_update_write_done(struct nfs_inode *nfsi, struct nfs_write_dat
{
#ifdef CONFIG_NFS_V4_1
pnfs_update_last_write(nfsi, data->args.offset, data->res.count);
- pnfs_need_layoutcommit(nfsi, data->args.context);
#endif /* CONFIG_NFS_V4_1 */
}
--
1.7.2.1
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
