Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2954019imu; Mon, 19 Nov 2018 08:33:47 -0800 (PST) X-Google-Smtp-Source: AJdET5dQ+6qv7TTpoRFwOkGf1N0exrEnR5XfudOut5lqoPeh7BKLgs55tAi8M4GWFG67ceD7jxkt X-Received: by 2002:a62:647:: with SMTP id 68-v6mr24554119pfg.42.1542645227197; Mon, 19 Nov 2018 08:33:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542645227; cv=none; d=google.com; s=arc-20160816; b=vRaxcfC/OxS+ewLT+oQEUKnRAP8rjVTCEGSOOTps21UE1esg58zBuGiNRQU31Gpxul sWoFA0lEZH0ZjOngQ06Fpx9NjJqh2tiVP+WPlwPN3gR2uWYUm0P3068bZDeh9L8w4nhW wAxRaxkSvgoUEKOFsBU29ZmYyZQZepqAAzPcRVO0hXBkSHWjzttkG6b00araDob6SmqO OwjiUBFrkwHwC70zaMUJpNbj3n23ycyWCZlnPavLyc8U4nYdVmm2ca1NJccf617uhdjK 1F7QFjqd6BEcqcK/cmJlCcRx3m2a3MfbBxKZaANwizS5dydLHuuoOs8lZ78ZSZ4h09L7 8IRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=gmqxQG5Fbsu5HyqewvU8QOgHlWb851+MO05YzSnA8Po=; b=ae3RRX3OYS//Klnk9jx3nECMsKBIRppRUHsciq4aZ87kzO4nqE3f5wDkTWHZQIM//q d3UjYRSCgNrOpIxHaoPpsWFQozh9WtrcdWDOmu5cUecl9LIi2xghG4A6WeSUwwH8sHhw VP+D/qZJ3mm+nJpl9ufu2zKE66w/9P518GEtrotvRm0mJVzXAJPP4nIqIPfkBL3Nizl3 3T3R5gF58qfelrBoYlS6UMfH+snLfmuqYKPiJ869J9OENvLT5CjTVRF5mfp6n7SdgeHT KHR8cT+cwqzEN/lXpPB4nlCqtWHxBk4Sqxu3xrrmpYCK3zHygJBIqVPb2vxVCcOHfVf1 fPEQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=K5xntIsF; 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 ay1si9417444plb.410.2018.11.19.08.33.30; Mon, 19 Nov 2018 08:33:47 -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; dkim=pass header.i=@kernel.org header.s=default header.b=K5xntIsF; 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 S1730670AbeKTC4U (ORCPT + 99 others); Mon, 19 Nov 2018 21:56:20 -0500 Received: from mail.kernel.org ([198.145.29.99]:54466 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729986AbeKTC4T (ORCPT ); Mon, 19 Nov 2018 21:56:19 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BFF1220831; Mon, 19 Nov 2018 16:32:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1542645132; bh=UOUbMG6JTK5p+/RSpta4xzAcdiUEFZPAn9lahf5ysgE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=K5xntIsF3Us+O78iK0Rlp5KkiqB+MI/YNQ4ci/vhWu4B7Bu211+ZbX4bbq53FsnGH MTiGxLNgHGXnbyaCkU/vZYaDVZii7jBJoODOYGV1ASfqefZ3i+RiYThGgcAljGEdC7 juhdWzsBZ+KmwEhmAPFRWJ38Vt2tuR/4ehm5pDdY= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Miklos Szeredi Subject: [PATCH 4.19 048/205] ovl: check whiteout in ovl_create_over_whiteout() Date: Mon, 19 Nov 2018 17:25:55 +0100 Message-Id: <20181119162625.920232189@linuxfoundation.org> X-Mailer: git-send-email 2.19.1 In-Reply-To: <20181119162616.586062722@linuxfoundation.org> References: <20181119162616.586062722@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.19-stable review patch. If anyone has any objections, please let me know. ------------------ From: Miklos Szeredi commit 5e1275808630ea3b2c97c776f40e475017535f72 upstream. Kaixuxia repors that it's possible to crash overlayfs by removing the whiteout on the upper layer before creating a directory over it. This is a reproducer: mkdir lower upper work merge touch lower/file mount -t overlay overlay -olowerdir=lower,upperdir=upper,workdir=work merge rm merge/file ls -al merge/file rm upper/file ls -al merge/ mkdir merge/file Before commencing with a vfs_rename(..., RENAME_EXCHANGE) verify that the lookup of "upper" is positive and is a whiteout, and return ESTALE otherwise. Reported by: kaixuxia Signed-off-by: Miklos Szeredi Fixes: e9be9d5e76e3 ("overlay filesystem") Cc: # v3.18 Signed-off-by: Greg Kroah-Hartman --- fs/overlayfs/dir.c | 4 ++++ 1 file changed, 4 insertions(+) --- a/fs/overlayfs/dir.c +++ b/fs/overlayfs/dir.c @@ -463,6 +463,10 @@ static int ovl_create_over_whiteout(stru if (IS_ERR(upper)) goto out_unlock; + err = -ESTALE; + if (d_is_negative(upper) || !IS_WHITEOUT(d_inode(upper))) + goto out_dput; + newdentry = ovl_create_temp(workdir, cattr); err = PTR_ERR(newdentry); if (IS_ERR(newdentry))