Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp671169ybz; Fri, 1 May 2020 06:33:17 -0700 (PDT) X-Google-Smtp-Source: APiQypK8usnjAjgcifx+OJyKc2PdxzNeejc56a9wfsdI8ZH4kqzYRhdYlaYXf5c1DlilTlGvNSHm X-Received: by 2002:aa7:c643:: with SMTP id z3mr3432090edr.154.1588339997024; Fri, 01 May 2020 06:33:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588339997; cv=none; d=google.com; s=arc-20160816; b=nADagQPlJMlggKqEkMgX8w2p5ZmnkVg5BhLjxtGGGhgfJ4xfGlYjaXgBlmvpQJZg4q raK5FUNwu3Ux8zmWNdRhxeGbGUUGgmK+5jKVuuYgRbNNdEqeGteevzv0whIpttx6tyws ydhspxAyw0kiQUSvsktSSt+jv4M0R+u4mXlYZFd8SfIYW1lg0eoMEnJgMguRPlRDT3Uv 5JzynirxfTK3WuLgaUke3GPIICOTxnHB4XPbnh4kom2bBJtL66BYxUa62xSKCdnVVU5Z ruKmYBVcKTcB62mcdT3iCrSnUXhEeoZ7lKNCSMy1akkJIXw1cdSkKtUxY3MGGXLd+T4M oRHQ== 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=kLu0pxNwh+zVXMRMmhRgMp9gnnGbhboRdRBiX66HZuk=; b=hq0Fr7vQePd3LbImialZc6NCu+gfSWOaV0pG79Ljs2k9S3rQBilnOXiC5n9qr05j/X XyACvOwkWkjEBttLyBGu8i8RcPGAO5HtKMFua+1vpBa+txS0yUhhMWzULzS52DqxZ/H0 O0IHaEW0gdug4PD/JMHlPgZpHL7Kf10EAXzRn1pHK7ntwKctZ1QUc8pQ2FhSygI/D1Vj 5hA3DBbhNd84jY8zPt/o2KxCpkLOHk+cEcPZbbiwAVuV29A9iyQmtmECboodTBEzSpPu NTCKI32OI1ID95eyBPn7sF/T0ETtIAFAp2xb4aEU66Uyw562f/x61vtvP3El0m09bBIB xl1Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=VUlWhGjR; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t27si1693626edt.42.2020.05.01.06.32.53; Fri, 01 May 2020 06:33:17 -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=@kernel.org header.s=default header.b=VUlWhGjR; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729959AbgEANad (ORCPT + 99 others); Fri, 1 May 2020 09:30:33 -0400 Received: from mail.kernel.org ([198.145.29.99]:54584 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729956AbgEANaa (ORCPT ); Fri, 1 May 2020 09:30:30 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.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 783A020757; Fri, 1 May 2020 13:30:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1588339829; bh=RnHZ55ZQd+oFxIjGZK85Q+Q5EPPSaa4vig9BLZFgBww=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=VUlWhGjRoVjClL4HtIUbqvjFdEzJ9om1aYx4C2aSLqxVj4loO1Dvim0uWaRPXibpQ 4j/ofyC+sNNeMVl7PKsoMQT9Jg2761Cb5Yqn5XqAZ1ENUENlIXfIRPEOQ53pd8lyNW A5N3oqfEl67UHFebfWdm7hro4UDRaNChQo4a/4j4= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Dan Rue , Theodore Tso , Naresh Kamboju , Ashwin H Subject: [PATCH 4.9 77/80] ext4: dont perform block validity checks on the journal inode Date: Fri, 1 May 2020 15:22:11 +0200 Message-Id: <20200501131537.255299635@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200501131513.810761598@linuxfoundation.org> References: <20200501131513.810761598@linuxfoundation.org> User-Agent: quilt/0.66 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: Theodore Ts'o commit 0a944e8a6c66ca04c7afbaa17e22bf208a8b37f0 upstream. Since the journal inode is already checked when we added it to the block validity's system zone, if we check it again, we'll just trigger a failure. This was causing failures like this: [ 53.897001] EXT4-fs error (device sda): ext4_find_extent:909: inode #8: comm jbd2/sda-8: pblk 121667583 bad header/extent: invalid extent entries - magic f30a, entries 8, max 340(340), depth 0(0) [ 53.931430] jbd2_journal_bmap: journal block not found at offset 49 on sda-8 [ 53.938480] Aborting journal on device sda-8. ... but only if the system was under enough memory pressure that logical->physical mapping for the journal inode gets pushed out of the extent cache. (This is why it wasn't noticed earlier.) Fixes: 345c0dbf3a30 ("ext4: protect journal inode's blocks using block_validity") Reported-by: Dan Rue Signed-off-by: Theodore Ts'o Tested-by: Naresh Kamboju Signed-off-by: Ashwin H Signed-off-by: Greg Kroah-Hartman --- fs/ext4/extents.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) --- a/fs/ext4/extents.c +++ b/fs/ext4/extents.c @@ -554,10 +554,14 @@ __read_extent_tree_block(const char *fun } if (buffer_verified(bh) && !(flags & EXT4_EX_FORCE_CACHE)) return bh; - err = __ext4_ext_check(function, line, inode, - ext_block_hdr(bh), depth, pblk); - if (err) - goto errout; + if (!ext4_has_feature_journal(inode->i_sb) || + (inode->i_ino != + le32_to_cpu(EXT4_SB(inode->i_sb)->s_es->s_journal_inum))) { + err = __ext4_ext_check(function, line, inode, + ext_block_hdr(bh), depth, pblk); + if (err) + goto errout; + } set_buffer_verified(bh); /* * If this is a leaf block, cache all of its entries