From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,T_DKIMWL_WL_HIGH,URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3FC5BC28CC0 for ; Thu, 30 May 2019 03:48:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1500F248FA for ; Thu, 30 May 2019 03:48:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559188098; bh=w7+AWPVuzZQpjG6mkDajShr3EJ30H0mKphqY5xkQPN0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=OwiGBz5xRJbHalF9sZ39pCJmBtf2z1KLuL1cnvr2kV951309AxW5gP5srdpUwHLmK H7JNzoE+iKYsAXoQ6UPYrPRz5pHJwYKVCdnyYWdplLvKTdBPjFp8fJ+06opiKuvTvA vlFrJu12bz37GIsmwRfbfde5mKu1QrX54j5Fk83Y= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732739AbfE3DsM (ORCPT ); Wed, 29 May 2019 23:48:12 -0400 Received: from mail.kernel.org ([198.145.29.99]:58372 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732181AbfE3DUX (ORCPT ); Wed, 29 May 2019 23:20:23 -0400 Received: from localhost (ip67-88-213-2.z213-88-67.customer.algx.net [67.88.213.2]) (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 C5F132490A; Thu, 30 May 2019 03:20:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559186422; bh=w7+AWPVuzZQpjG6mkDajShr3EJ30H0mKphqY5xkQPN0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=DHU4ufS6mV725DkTPtn0jp/Jm+0l+3eOGZ7LEaOSm7PYPwnzsJVqhfhiaQD+KLpKY 5JAie7997IyyLE6OuEU5sKR/DkYqJtBLY3Lq3QF0DdV+xA8BVob7yDiUKee90s0v3r dCmQdqmTrQNXqWaXXVXv2LdAy4V3lBHDmH3l7t74= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Ira Weiny , Jan Kara , Theodore Tso , stable@kernel.org Subject: [PATCH 4.9 001/128] ext4: do not delete unlinked inode from orphan list on failed truncate Date: Wed, 29 May 2019 20:05:33 -0700 Message-Id: <20190530030433.176015804@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190530030432.977908967@linuxfoundation.org> References: <20190530030432.977908967@linuxfoundation.org> User-Agent: quilt/0.66 X-stable: review X-Patchwork-Hint: ignore 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 From: Jan Kara commit ee0ed02ca93ef1ecf8963ad96638795d55af2c14 upstream. It is possible that unlinked inode enters ext4_setattr() (e.g. if somebody calls ftruncate(2) on unlinked but still open file). In such case we should not delete the inode from the orphan list if truncate fails. Note that this is mostly a theoretical concern as filesystem is corrupted if we reach this path anyway but let's be consistent in our orphan handling. Reviewed-by: Ira Weiny Signed-off-by: Jan Kara Signed-off-by: Theodore Ts'o Cc: stable@kernel.org Signed-off-by: Greg Kroah-Hartman --- fs/ext4/inode.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/fs/ext4/inode.c +++ b/fs/ext4/inode.c @@ -5223,7 +5223,7 @@ int ext4_setattr(struct dentry *dentry, up_write(&EXT4_I(inode)->i_data_sem); ext4_journal_stop(handle); if (error) { - if (orphan) + if (orphan && inode->i_nlink) ext4_orphan_del(NULL, inode); goto err_out; }