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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Ted Tso <tytso@xxxxxxx>
Subject: [PATCH 0/4] ext4: Check journal inode extents more carefully
From: Jan Kara <jack@xxxxxxx>
Date: Wed, 15 Jul 2020 15:18:08 +0200
Cc: <linux-ext4@xxxxxxxxxxxxxxx>, Ritesh Harjani <riteshh@xxxxxxxxxxxxx>, Wolfgang Frisch <wolfgang.frisch@xxxxxxxx>, Jan Kara <jack@xxxxxxx>

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

Follow-Ups:
- [PATCH 3/4] ext4: Check journal inode extents more carefully
  - From: Jan Kara
- [PATCH 4/4] ext4: Fold ext4_data_block_valid_rcu() into the caller
  - From: Jan Kara
- [PATCH 2/4] ext4: Don't allow overlapping system zones
  - From: Jan Kara
- [PATCH 1/4] ext4: Handle error of ext4_setup_system_zone() on remount
  - From: Jan Kara

Prev by Date: Re: [PATCH] ext4: catch integer overflow in ext4_cache_extents
Next by Date: [PATCH 1/4] ext4: Handle error of ext4_setup_system_zone() on remount
Previous by thread: ext4: fix spelling typos in ext4_mb_initialize_context
Next by thread: [PATCH 1/4] ext4: Handle error of ext4_setup_system_zone() on remount
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]

Powered by Linux