From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [RFC PATCH 0/2] Fix up the NFS mmap code Date: Sat, 9 Jan 2010 02:40:05 +0000 Message-ID: <20100109024005.GI30528@ZenIV.linux.org.uk> References: <1262913974.2659.101.camel@localhost> <20100109005624.7473.33215.stgit@localhost.localdomain> <20100109013825.GD30528@ZenIV.linux.org.uk> <20100109021124.GG30528@ZenIV.linux.org.uk> <20100109023035.GH30528@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Trond Myklebust , Andi Kleen , linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org To: Linus Torvalds Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:52383 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752584Ab0AICkM (ORCPT ); Fri, 8 Jan 2010 21:40:12 -0500 In-Reply-To: <20100109023035.GH30528@ZenIV.linux.org.uk> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Sat, Jan 09, 2010 at 02:30:35AM +0000, Al Viro wrote: > Interesting... There's nfs_update_inode(), but it ought to scream bloody > murder on the type change (and its return value is ignore by nfs_fhget(), > BTW). Uh-oh... Just what will happen if we get FATTR_MODE without FATTR_TYPE, BTW? AFAICS, the check for changed type won't trigger, but we will get type bits in i_mode set to 0. Probably unrelated, but...