From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750883AbWH2BaV (ORCPT ); Mon, 28 Aug 2006 21:30:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750905AbWH2BaU (ORCPT ); Mon, 28 Aug 2006 21:30:20 -0400 Received: from ns1.suse.de ([195.135.220.2]:904 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1750867AbWH2BaU (ORCPT ); Mon, 28 Aug 2006 21:30:20 -0400 From: NeilBrown To: Andrew Morton Date: Tue, 29 Aug 2006 11:30:15 +1000 X-face: [Gw_3E*Gng}4rRrKRYotwlE?.2|**#s9D, linux-kernel@vger.kernel.org Subject: [PATCH 000 of 2] Invalidate_inode_pages2 changes. Message-ID: <20060829111641.18391.patches@notabene> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi all, I'm picking up on a conversation that was started in late March this year, and which didn't get anywhere much. See http://lkml.org/lkml/2006/3/31/93 and following. The issue is that it is possible for an NFS client to lose writes if a particular race is lost - and this has been seen in real life. The patch discussed in the above mentioned converstation made two changes, one of which was completely right. The over was slightly wrong. Having explored the issue in some depth I now see how it was wrong and present below for your enjoyment two patches. One which makes and justifies the first change. One which makes and justifies a revised version of the second change. Thanks, NeilBrown [PATCH 001 of 2] Invalidate_inode_pages2 shouldn't abort on first error. [PATCH 002 of 2] Make data destruction in invalidate_inode_pages2 optional.