From: Theodore Tso <tytso@MIT.EDU>
To: kalpak@clusterfs.com
Cc: linux-ext4@vger.kernel.org
Subject: [PATCH 0 of 4] Check journal inode sanity and recreate journal
Date: Thu, 21 Jun 2007 13:00:07 -0400 [thread overview]
Message-ID: <patchbomb.1182445207@candygram.thunk.org> (raw)
Hi Kalpak,
I've broken up your patch and rewritten portions of them to
clean them up. As I've mentioned before, smaller patches are easier to
review and to cherry pick as necessary.
The changes from your patches are:
1) A smaller set of functionality (just returning the recommended
default size of the journal) was moved into the library. This
eliminated the need to create a number of new libext2fs error codes,
and it minimized the changes needed to tune2fs and mke2fs.
2) Your changes to sanity check the journal blocks beyond the location
of the indirect blocks used journal_bmap(); unfortunately
journal_bmap doesn't verify the validity of the indirect/double
indirect blocks. So, I rewrote the checks to use
ext2fs_block_iterate() instead, which was designed for use by e2fsck.
It basically was a (very) simplified version of check_blocks() from
pass1.c. Your patch also didn't remove the original code which just
verified the direct blocks, which was no longer necessary, and
performed the check after the backup blocks and be written out to the
journal, instead of before deciding to overwrite the journal inode
with the backup information from the superblock.
Regards,
- Ted
11 files changed, 144 insertions(+), 39 deletions(-)
e2fsck/journal.c | 67 ++++++++++++++++++++++++++++++-----------
e2fsck/problem.c | 5 +++
e2fsck/problem.h | 7 ++++
e2fsck/unix.c | 40 ++++++++++++++++++++++++
lib/ext2fs/ext2fs.h | 1
lib/ext2fs/mkjournal.c | 20 ++++++++++++
misc/util.c | 23 +++-----------
tests/f_badjourblks/expect.1 | 8 ++++
tests/f_badjourblks/expect.2 | 2 -
tests/f_miss_journal/expect.1 | 8 ++++
tests/f_miss_journal/expect.2 | 2 -
next reply other threads:[~2007-06-21 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 17:00 Theodore Tso [this message]
2007-06-21 17:00 ` [PATCH 1 of 4] Add default journal size function Theodore Tso
2007-06-21 17:00 ` [PATCH 2 of 4] Recreate journal that had been removed previously due to corruption Theodore Tso
2007-06-21 17:00 ` [PATCH 3 of 4] Write the updated journal inode if s_jnl_blocks was successfully used Theodore Tso
2007-06-21 17:00 ` [PATCH 4 of 4] e2fsck: Check the all of journal blocks for validity Theodore Tso
2007-06-21 20:45 ` [PATCH 0 of 4] Check journal inode sanity and recreate journal Kalpak Shah
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=patchbomb.1182445207@candygram.thunk.org \
--to=tytso@mit.edu \
--cc=kalpak@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
/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