[0/4] ext4: Check journal inode extents more carefully

Message ID	20200715131812.7243-1-jack@suse.cz
Headers	show Return-Path: <linux-ext4-owner@vger.kernel.org> From: Jan Kara <jack@suse.cz> To: Ted Tso <tytso@mit.edu> Cc: <linux-ext4@vger.kernel.org>, Ritesh Harjani <riteshh@linux.ibm.com>, Wolfgang Frisch <wolfgang.frisch@suse.com>, Jan Kara <jack@suse.cz> Subject: [PATCH 0/4] ext4: Check journal inode extents more carefully Date: Wed, 15 Jul 2020 15:18:08 +0200 Message-Id: <20200715131812.7243-1-jack@suse.cz> Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk
Series	ext4: Check journal inode extents more carefully \| expand [0/4] ext4: Check journal inode extents more carefully [1/4] ext4: Handle error of ext4_setup_system_zone() on remount [2/4] ext4: Don't allow overlapping system zones [3/4] ext4: Check journal inode extents more carefully [4/4] ext4: Fold ext4_data_block_valid_rcu() into the caller

Message ID

20200715131812.7243-1-jack@suse.cz

Headers

From: Jan Kara <jack@suse.cz>
To: Ted Tso <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>,
        Ritesh Harjani <riteshh@linux.ibm.com>,
        Wolfgang Frisch <wolfgang.frisch@suse.com>,
        Jan Kara <jack@suse.cz>
Subject: [PATCH 0/4] ext4: Check journal inode extents more carefully
Date: Wed, 15 Jul 2020 15:18:08 +0200
Message-Id: <20200715131812.7243-1-jack@suse.cz>
Sender: linux-ext4-owner@vger.kernel.org
Precedence: bulk

Series

ext4: Check journal inode extents more carefully | expand

Message

Jan Kara July 15, 2020, 1:18 p.m. UTC

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. 

								Honza