Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp447256pxb; Wed, 3 Mar 2021 07:14:00 -0800 (PST) X-Google-Smtp-Source: ABdhPJyo+bH5r954eDECXcZyrFzHIhymvBqrAS18G9VSfTV/O9Kb4seCnDv2m4dVPlvuRInODwQ/ X-Received: by 2002:a17:907:76bb:: with SMTP id jw27mr25897901ejc.366.1614784440531; Wed, 03 Mar 2021 07:14:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614784440; cv=none; d=google.com; s=arc-20160816; b=SmZWDkJ7UPrEvtB3itOSp1PpfHErBUt+/nwfi2PF3GwtBu2jHHgs6ybpA0ZJ7H8eiH jrUPK1mnusIRQa2o55dVhKpDSa7ilDMj/ruG22PRqpyxV3Skf8eaGdxjUqwPXIAOjQeO b3KAttOH7hsrAUORfVrFqxVGIl1X2262jzd9n3EU5hNT1wEvNzW9Jxt3WrPgd7GNt6Tx aXcpQ8rrcXvOJiXgsvDikzoa3Fy8QxtOP+8SKkXYpks7h+AuyOR4+F720W1LZBNH6cen 5hN2PL77cohVEwZPujhTK3CsgjeOFTZsZiKSH1MTvpSoizNyTeILqhGnzAG9ZG89aecY 2caw== 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=9eQTZ01XHtNUCYGKnyYEVffaVTQzi9qXzw2Kpn3MS/c=; b=qiJMzzrP2X9MYpsNqLgiybadVA3gwhiDk1nvHo2QM4XcvOKKL/08oG0Pc9O+ieAtEV gh5MDSP2SMMpLgVqAs2UIKRN1CIevTetvfsLQOzAHB4vaxS8xHJ7ow/pWzvlmW3MKPUX Y/hpLC3JoFtfUkNHxOnpOMlsuxYTAB56q0oHh40tX7pe9JkRgkBN2RuPJv5/9tTCg7p0 kwBX9MJNo1q++u9FaYn+VGdyPi1aRTYE8lxtAPKq4XpfHueM91pbk9dzWV9XjxBJd0j8 QQF+ak8bCbHF+lmrSEN0Ui1ceMe8vWQKw0Go991O+ZkVI/z895MIpMDqIftJoN9aEci2 OQDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=eYt796bQ; 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 o16si15427774eds.116.2021.03.03.07.13.29; Wed, 03 Mar 2021 07:14:00 -0800 (PST) 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=eYt796bQ; 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 S1343547AbhCAWgy (ORCPT + 99 others); Mon, 1 Mar 2021 17:36:54 -0500 Received: from mail.kernel.org ([198.145.29.99]:32854 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238364AbhCARmK (ORCPT ); Mon, 1 Mar 2021 12:42:10 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 35BCE650CF; Mon, 1 Mar 2021 16:57:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1614617830; bh=l7UsS6s+geSISZVWy4Wdx/lWP2smWsWtS3a0K5VpQ5o=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=eYt796bQ4bxDSIk6JqdMEWg+ASGf8vPevxqVY1Lqa1tSN4QMaSZKGKVxDeCdPxanR vAkOpVb58MSEnq5jAUsv43x1mLnD8hxN9+3IDRV+hfYpXanTfXmSS8sQwgv1kW/pTB jf2/nOpWShssjyAdZyIYRcG4QrZyjd09aKsa9QFI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Artem Blagodarenko , Theodore Tso , Sasha Levin Subject: [PATCH 5.4 212/340] ext4: fix potential htree index checksum corruption Date: Mon, 1 Mar 2021 17:12:36 +0100 Message-Id: <20210301161058.734542176@linuxfoundation.org> X-Mailer: git-send-email 2.30.1 In-Reply-To: <20210301161048.294656001@linuxfoundation.org> References: <20210301161048.294656001@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: Theodore Ts'o [ Upstream commit b5776e7524afbd4569978ff790864755c438bba7 ] In the case where we need to do an interior node split, and immediately afterwards, we are unable to allocate a new directory leaf block due to ENOSPC, the directory index checksum's will not be filled in correctly (and indeed, will not be correctly journalled). This looks like a bug that was introduced when we added largedir support. The original code doesn't make any sense (and should have been caught in code review), but it was hidden because most of the time, the index node checksum will be set by do_split(). But if do_split bails out due to ENOSPC, then ext4_handle_dirty_dx_node() won't get called, and so the directory index checksum field will not get set, leading to: EXT4-fs error (device sdb): dx_probe:858: inode #6635543: block 4022: comm nfsd: Directory index failed checksum Google-Bug-Id: 176345532 Fixes: e08ac99fa2a2 ("ext4: add largedir feature") Cc: Artem Blagodarenko Signed-off-by: Theodore Ts'o Signed-off-by: Sasha Levin --- fs/ext4/namei.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c index f05ec9bfbf4fd..7f22487d502b5 100644 --- a/fs/ext4/namei.c +++ b/fs/ext4/namei.c @@ -2405,11 +2405,10 @@ again: (frame - 1)->bh); if (err) goto journal_error; - if (restart) { - err = ext4_handle_dirty_dx_node(handle, dir, - frame->bh); + err = ext4_handle_dirty_dx_node(handle, dir, + frame->bh); + if (err) goto journal_error; - } } else { struct dx_root *dxroot; memcpy((char *) entries2, (char *) entries, -- 2.27.0