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=-4.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 B45CBC433DF for ; Fri, 7 Aug 2020 05:01:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9E0C62086A for ; Fri, 7 Aug 2020 05:01:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726123AbgHGFBT (ORCPT ); Fri, 7 Aug 2020 01:01:19 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:57611 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725263AbgHGFBT (ORCPT ); Fri, 7 Aug 2020 01:01:19 -0400 Received: from callcc.thunk.org (pool-96-230-252-158.bstnma.fios.verizon.net [96.230.252.158]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 07751B7H015516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 7 Aug 2020 01:01:11 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id E2A11420263; Fri, 7 Aug 2020 01:01:10 -0400 (EDT) Date: Fri, 7 Aug 2020 01:01:10 -0400 From: tytso@mit.edu To: Jan Kara Cc: Subject: Re: [PATCH 0/6 v3] ext4: Check journal inode extents more carefully Message-ID: <20200807050110.GS7657@mit.edu> References: <20200728130437.7804-1-jack@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200728130437.7804-1-jack@suse.cz> Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Tue, Jul 28, 2020 at 03:04:31PM +0200, Jan Kara wrote: > Hello! > > This series changes ext4 to properly check extent tree blocks of journal inode. > Omitting these (which is a limitation of block validity checks) leads to crash > in ext4_cache_extents() in case the extent tree of the journal inode is > suitably corrupted. Thanks, I've applied this series. - Ted