Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp3120090ybx; Sun, 3 Nov 2019 11:12:16 -0800 (PST) X-Google-Smtp-Source: APXvYqxD9y5VF21acMIzQygE2I5cChyKJoTqvq4gP7eoZ5TDNUS2g6fqzOeqr3geLlKvk0W/iXI6 X-Received: by 2002:a50:cb86:: with SMTP id k6mr25515891edi.270.1572808335979; Sun, 03 Nov 2019 11:12:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1572808335; cv=none; d=google.com; s=arc-20160816; b=RmB9DriKD1M2aFPH5RRyQmV2w53Caed+ZNwR7IhYszD3bwlXBQwHksKHWdFVq4uky0 U/rcETBdvnBI1K2haJPA1hG4CpXm+QARSFhWxqhk7CzYk45ALj8fDKeGm+1aC2SureGV tVGZZ5zg2Uyasqn8lqOsbNZE9fWk+axYIRmYMVAH0o2ovJEC7pdhZW22VtrwSou/ZP7g Oz+iGneNjRjYEskpDqSlcSs0ZNSsBziw6KREBwtx69iJA9+6tvZzqkhifkwG+HEv3o1v A7nvxoCKRVUEFgS2vdWI39fekOdvQJKmuOaW3kP06OpdNNOjRRtpJ8ItpxF1ocstGsHc a/Ug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ovo7V9n2+B4g8vpkoaEs0TsHpO+Q1IjaDPgjaH+zo6A=; b=MLwAnMtZCnfWy4qx6kIMMbrjCEhFndFUE6YvabYzBvr5JAzsMqZQCHfYIY6aA9glfI fVHDNhzlw0479yd5ZDYvMYR5jII3gNGPDR5P6qK2U0UduKM/Xyq0gtKrbG+7FKJUIidI yQg0F9DeeF5uP4maf0GJog0P8ST4hsCBoQ5Qr6QCUqfsE/MYboWCZyBz3ikkE4M+zObE UEmnlyc5Im3oDO4u3BwzPOmfLXtRh2q00HMJf0rQkpWwsxN1K2cfMZm5oxcWvhqwJPg8 GCQLIDqCX1lzrvr+ECMvqja3RXrsNpfTd3yjK56oy/uN8QQir+VoKU1GgiivQpWQm5VR eCdg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q4si6059074edc.403.2019.11.03.11.11.50; Sun, 03 Nov 2019 11:12:15 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728090AbfKCTDZ (ORCPT + 99 others); Sun, 3 Nov 2019 14:03:25 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:40918 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727322AbfKCTDZ (ORCPT ); Sun, 3 Nov 2019 14:03:25 -0500 Received: from viro by ZenIV.linux.org.uk with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1iRL9n-0003sS-Ft; Sun, 03 Nov 2019 19:03:23 +0000 Date: Sun, 3 Nov 2019 19:03:23 +0000 From: Al Viro To: linux-fsdevel@vger.kernel.org Cc: Ritesh Harjani , linux-kernel@vger.kernel.org, wugyuan@cn.ibm.com, jlayton@kernel.org, hsiangkao@aol.com, Jan Kara , Linus Torvalds , ecryptfs@vger.kernel.org Subject: [PATCH][RFC] ecryptfs_lookup_interpose(): lower_dentry->d_parent is not stable either Message-ID: <20191103190323.GS26530@ZenIV.linux.org.uk> References: <20191022133855.B1B4752050@d06av21.portsmouth.uk.ibm.com> <20191022143736.GX26530@ZenIV.linux.org.uk> <20191022201131.GZ26530@ZenIV.linux.org.uk> <20191023110551.D04AE4C044@d06av22.portsmouth.uk.ibm.com> <20191101234622.GM26530@ZenIV.linux.org.uk> <20191102172229.GT20975@paulmck-ThinkPad-P72> <20191102180842.GN26530@ZenIV.linux.org.uk> <20191103163524.GO26530@ZenIV.linux.org.uk> <20191103182058.GQ26530@ZenIV.linux.org.uk> <20191103185133.GR26530@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191103185133.GR26530@ZenIV.linux.org.uk> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We need to get the underlying dentry of parent; sure, absent the races it is the parent of underlying dentry, but there's nothing to prevent losing a timeslice to preemtion in the middle of evaluation of lower_dentry->d_parent->d_inode, having another process move lower_dentry around and have its (ex)parent not pinned anymore and freed on memory pressure. Then we regain CPU and try to fetch ->d_inode from memory that is freed by that point. dentry->d_parent *is* stable here - it's an argument of ->lookup() and we are guaranteed that it won't be moved anywhere until we feed it to d_add/d_splice_alias. So we safely go that way to get to its underlying dentry. Cc: stable@vger.kernel.org # since 2009 or so Signed-off-by: Al Viro diff --git a/fs/ecryptfs/inode.c b/fs/ecryptfs/inode.c index 3c2298721359..e23752d9a79f 100644 --- a/fs/ecryptfs/inode.c +++ b/fs/ecryptfs/inode.c @@ -319,9 +319,9 @@ static int ecryptfs_i_size_read(struct dentry *dentry, struct inode *inode) static struct dentry *ecryptfs_lookup_interpose(struct dentry *dentry, struct dentry *lower_dentry) { + struct path *path = ecryptfs_dentry_to_lower_path(dentry->d_parent); struct inode *inode, *lower_inode; struct ecryptfs_dentry_info *dentry_info; - struct vfsmount *lower_mnt; int rc = 0; dentry_info = kmem_cache_alloc(ecryptfs_dentry_info_cache, GFP_KERNEL); @@ -330,13 +330,12 @@ static struct dentry *ecryptfs_lookup_interpose(struct dentry *dentry, return ERR_PTR(-ENOMEM); } - lower_mnt = mntget(ecryptfs_dentry_to_lower_mnt(dentry->d_parent)); fsstack_copy_attr_atime(d_inode(dentry->d_parent), - d_inode(lower_dentry->d_parent)); + d_inode(path->dentry)); BUG_ON(!d_count(lower_dentry)); ecryptfs_set_dentry_private(dentry, dentry_info); - dentry_info->lower_path.mnt = lower_mnt; + dentry_info->lower_path.mnt = mntget(path->mnt); dentry_info->lower_path.dentry = lower_dentry; /*