From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933328AbbCPWuq (ORCPT ); Mon, 16 Mar 2015 18:50:46 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:34641 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932961AbbCPWum (ORCPT ); Mon, 16 Mar 2015 18:50:42 -0400 Date: Mon, 16 Mar 2015 22:50:40 +0000 From: Al Viro To: NeilBrown Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 10/13] VFS/namei: handle LOOKUP_RCU in page_follow_link_light. Message-ID: <20150316225040.GG29656@ZenIV.linux.org.uk> References: <20150316043602.23648.52734.stgit@notabene.brown> <20150316044320.23648.90827.stgit@notabene.brown> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150316044320.23648.90827.stgit@notabene.brown> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 16, 2015 at 03:43:20PM +1100, NeilBrown wrote: > + char *kaddr; > + struct page *page; > + struct address_space *mapping = dentry->d_inode->i_mapping; Who said that dentry->d_inode hasn't gone NULL by that point? > + nd_terminate_link(kaddr, dentry->d_inode->i_size, PAGE_SIZE - 1); ... or changed here. Again, dentry->d_inode is stable only if you are holding a reference to dentry. That's why we have those dances around nd->inode, for example. Doing unlazy_walk() is enough to stabilize the damn thing, so currently ->follow_link() doesn't have to worry about it. With your changes, though...