From: Jan Kara <jack@suse.cz>
To: Ted Tso <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: [PATCH 0/6 v3] ext4: Check journal inode extents more carefully
Date: Tue, 28 Jul 2020 15:04:31 +0200 [thread overview]
Message-ID: <20200728130437.7804-1-jack@suse.cz> (raw)
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.
Changes since v1:
* Added Reviewed-by tags from Lukas
* Fixed two more unrelated minor bugs in block validity testing spotted by
Lukas
Changes since v2:
* Add more Reviewed-by tags from Lukas
* Fix intermediate compilation failure in patch 3/6
Honza
next reply other threads:[~2020-07-28 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 13:04 Jan Kara [this message]
2020-07-28 13:04 ` [PATCH 1/6] ext4: Handle error of ext4_setup_system_zone() on remount Jan Kara
2020-07-28 13:04 ` [PATCH 2/6] ext4: Don't allow overlapping system zones Jan Kara
2020-07-28 13:04 ` [PATCH 3/6] ext4: Check journal inode extents more carefully Jan Kara
2020-07-28 13:04 ` [PATCH 4/6] ext4: Fold ext4_data_block_valid_rcu() into the caller Jan Kara
2020-07-28 13:04 ` [PATCH 5/6] ext4: Handle add_system_zone() failure in ext4_setup_system_zone() Jan Kara
2020-07-28 13:04 ` [PATCH 6/6] ext4: Correctly restore system zone info when remount fails Jan Kara
2020-08-07 5:01 ` [PATCH 0/6 v3] ext4: Check journal inode extents more carefully tytso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200728130437.7804-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).