Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp2266484imm; Thu, 7 Jun 2018 07:57:56 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKRlGgkETphc//GuzcNyhU+b+UHgjdAvQReDtkIb2IanO5yhOUSiD0e2a78SvnBdN41VOyX X-Received: by 2002:a65:43cb:: with SMTP id n11-v6mr1863754pgp.234.1528383476477; Thu, 07 Jun 2018 07:57:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528383476; cv=none; d=google.com; s=arc-20160816; b=hVEpWRQ6k2MIzRLLMZ5xQSHPIEoIP7MVd+HQHw3Gm4RIstsWXTzHY/Y8uwxFxOAWnE /n0v8a07Ng/9applU9lzOCID3F/HxVb3jg9s3D7uY21IY5bSPbi0WWdkX2fijI2gPrXk Ff2KcYsLzMdxkfxSN0zgvABYwqqF7PqR/bQZUTlyR3wLGgWrdhfizGFR+iHEk+TBU4qd XA0gFwfXXAJbR2bHald657KtVt5w+WBW32/7AIy4/hiOgV6Htgu9mGJyFf15GSz9W3mn 1mDIwcEWi+/38R9G3PkmR28JxZdTg2VXg85l9UKJtOfWnU9HInAJu5yFxo1AOe9upoPr xlSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition :arc-authentication-results; bh=j+h76qLHVaHcVoRkd/X0MroXVK6F9lqnOeBdtNEJxnc=; b=uA/+RnDSCAQ+fZiirvjWUeTtKRSt2lQjXvqJk+zCE1Nff3uNrR63SjCrpOUOnujgYF ghHEL7Q7wmUNDz4pZFHn3S5P68lzfKYC3BXnG/KO2HqVVe4SNVR7dY83VPXbfqlIhAuU aEgkTQcXCOc3J1d3TxTgA1UBKsIM/WGRZDQ3kQoKuuDjKtgw425N7w1olYTvWC+b6Ig5 tBw7q2sl7D0BR9U6TSCUY449UH7Ri0jmoKEHHdHP0Nv+EzciZ3EpfgsWNA5zvZ7nQF5X 29RSQY0GEA/U5BqCak3V8Nib3lyeAmFDWnUgC8gjd88js5QuIAJfB7O797erGCczQ3j2 3sgg== 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 j193-v6si28721977pge.371.2018.06.07.07.57.42; Thu, 07 Jun 2018 07:57:56 -0700 (PDT) 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 S964792AbeFGOzZ (ORCPT + 99 others); Thu, 7 Jun 2018 10:55:25 -0400 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:41049 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935431AbeFGOzH (ORCPT ); Thu, 7 Jun 2018 10:55:07 -0400 Received: from [148.252.241.226] (helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1fQvbX-0005Zi-AJ; Thu, 07 Jun 2018 15:09:31 +0100 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1fQvb9-00037F-JO; Thu, 07 Jun 2018 15:09:07 +0100 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "Al Viro" Date: Thu, 07 Jun 2018 15:05:21 +0100 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) Subject: [PATCH 3.16 280/410] lock_parent() needs to recheck if dentry got __dentry_kill'ed under it In-Reply-To: X-SA-Exim-Connect-IP: 148.252.241.226 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.57-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Al Viro commit 3b821409632ab778d46e807516b457dfa72736ed upstream. In case when dentry passed to lock_parent() is protected from freeing only by the fact that it's on a shrink list and trylock of parent fails, we could get hit by __dentry_kill() (and subsequent dentry_kill(parent)) between unlocking dentry and locking presumed parent. We need to recheck that dentry is alive once we lock both it and parent *and* postpone rcu_read_unlock() until after that point. Otherwise we could return a pointer to struct dentry that already is rcu-scheduled for freeing, with ->d_lock held on it; caller's subsequent attempt to unlock it can end up with memory corruption. Signed-off-by: Al Viro Signed-off-by: Ben Hutchings --- fs/dcache.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) --- a/fs/dcache.c +++ b/fs/dcache.c @@ -590,11 +590,16 @@ again: spin_unlock(&parent->d_lock); goto again; } - rcu_read_unlock(); - if (parent != dentry) + if (parent != dentry) { spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED); - else + if (unlikely(dentry->d_lockref.count < 0)) { + spin_unlock(&parent->d_lock); + parent = NULL; + } + } else { parent = NULL; + } + rcu_read_unlock(); return parent; }