Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp3407095pxy; Mon, 26 Apr 2021 00:36:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwfoUzCPYIMMp6cbBqzAUbb3iIZXaL2OQWwZ95sQvHVKzGpijnIbkFPXlHQrsoODIBYUePT X-Received: by 2002:a17:902:dacd:b029:e5:cf71:3901 with SMTP id q13-20020a170902dacdb02900e5cf713901mr17016289plx.23.1619422616590; Mon, 26 Apr 2021 00:36:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619422616; cv=none; d=google.com; s=arc-20160816; b=02Fmm0uwyOyrP5wMeqRhZIsDCb1fb9gtpw5ZNnCKsCCFL7hBsDtERT+W039qShFGx7 NP8wg9FI1xoZAzZDoOR3n7A8bIxTyUZgbEMXcWL+EQHqPbLzPuzYQXQKw9rvbWI7tKq3 BHm2BYOPcjhBgKfQXBdfKXuNcvgI0KEaAfCfB6p9uF5notFI2tCl9gg+t6pfm5s8fuT3 9B7Gr2VL2T4gU8welqTsZCwr+oS6+Wf9tIcJfDkOrAv8fPRPR9y07IWjXYi66TgYM3wX dTlmfRO11At0hPSMwWDcNv05XvPUUNC/om2l5M5lWRgCVV2pGpIVeQmrJ3/JJa4JPxuk /5Rg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=DqSsjnNiDrtoE0Nria2neTYSbZQ1HpHx8sg0obHRkTw=; b=Vkly8SONgdVpecFveGv5vB5EBHeAD1afXvcbMJIUQo5JGGibJ4jQ8XVZGLDPplIu9h BMjr3pc9jOZPZn5HvA6Z1S1Y5FO726W3rGdaNG87ulo0I1kSUdtrSRMDITeZsdPkPLrO 7IEBSH8XrOuopCS05meeyz4ldNn3Q5PZ+eBw+oTWPMtiNclOqKt/W0mZ1JQmNTXqi9xs QAGNtMyFJWyBNXesSKpo6Hrst/Hy6sNHDc5wUl3iWbb4nzYylSDumBeRGyTUKSHnPP36 0jxi4f4LGwZmTSHpYYzhncOPEpYO/F7VEXEnf+5jZFCDph0PZFdwvueH8Lste0amlwIV cotw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=YhmayA44; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w22si14887389pgm.129.2021.04.26.00.36.43; Mon, 26 Apr 2021 00:36:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=YhmayA44; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232557AbhDZHgL (ORCPT + 99 others); Mon, 26 Apr 2021 03:36:11 -0400 Received: from mail.kernel.org ([198.145.29.99]:46254 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232721AbhDZHdt (ORCPT ); Mon, 26 Apr 2021 03:33:49 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id CEA5461004; Mon, 26 Apr 2021 07:33:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1619422387; bh=Jr1FW1DpEb/HpXC8WDF7LBl/NLMvAYSoaajw1ahahRk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=YhmayA44+own8pvStCx0otjs/prLv+RV4lTAUbbP6YFEWprPzDnFlxC5dtzhc2LeE GI/CqxZwYMu3kQKvHJqdnjxJJoowKLnSS9w9OZO2wBz6a3h9MYxYM98FKJiaZHxnHB qFjXutcDVZcpK9P/lt6Q0UQY5E4pfwfsDdkqAJeM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Greg Kroah-Hartman , Zhang Yi Subject: [PATCH 4.9 29/37] ext4: correct error label in ext4_rename() Date: Mon, 26 Apr 2021 09:29:30 +0200 Message-Id: <20210426072818.241680931@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210426072817.245304364@linuxfoundation.org> References: <20210426072817.245304364@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Zhang Yi The backport of upstream patch 5dccdc5a1916 ("ext4: do not iput inode under running transaction in ext4_rename()") introduced a regression on the stable kernels 4.14 and older. One of the end_rename error label was forgetting to change to release_bh, which may trigger below bug. ------------[ cut here ]------------ kernel BUG at /home/zhangyi/hulk-4.4/fs/ext4/ext4_jbd2.c:30! ... Call Trace: [] ext4_rename+0x9e2/0x10c0 [] ? unlazy_walk+0x124/0x2a0 [] ext4_rename2+0x25/0x60 [] vfs_rename+0x3a4/0xed0 [] SYSC_renameat2+0x57d/0x7f0 [] SyS_renameat+0x19/0x30 [] entry_SYSCALL_64_fastpath+0x18/0x78 ... ---[ end trace 75346ce7c76b9f06 ]--- Fixes: f5337ec530a6 ("ext4: do not iput inode under running transaction in ext4_rename()") Signed-off-by: Zhang Yi Signed-off-by: Greg Kroah-Hartman --- fs/ext4/namei.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/fs/ext4/namei.c +++ b/fs/ext4/namei.c @@ -3621,7 +3621,7 @@ static int ext4_rename(struct inode *old ext4_encrypted_inode(new.dir) && !fscrypt_has_permitted_context(new.dir, old.inode)) { retval = -EXDEV; - goto end_rename; + goto release_bh; } new.bh = ext4_find_entry(new.dir, &new.dentry->d_name,