From: Theodore Tso <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2fsprogs: Handle rec_len correctly for 64KB blocksize
Date: Mon, 12 Nov 2007 09:58:23 -0500 [thread overview]
Message-ID: <20071112145823.GB17462@thunk.org> (raw)
In-Reply-To: <20071112095245.GA1465@duck.suse.cz>
On Mon, Nov 12, 2007 at 10:52:45AM +0100, Jan Kara wrote:
> > Did you test this patch before submitting it?
>
> Argh, stupid me. I've just tested that I didn't break anything for normal
> block size and thought that I cannot make mistake in such a simple thing
> ;).
Could I ask you to perhaps include some 64k blocksize test cases that
would exercise the new codepaths?
> > The only way to do this is to find all of the places that reference
> > rec_len, and do the check there.
> Yes.. Thanks for having look.
One suggestion is that instead of just creating an conversion
function, and then doing a global search and replace, in some places
it might be better to declare an integer variable, and then assign
"rec_len = ext2fs_rec_len_from_disk(dirent->rec_len)". For example,
that would make ext2fs_process_dir_block() more readable, where
dirent->rec_len is used no less than eight times.
Thanks, and my apologies for not having time to review the patch until
now. At the moment things are a bit crazy since I am effectively
doing two jobs, since I am in transition between two assignments, and
me doing most of both of them at the moment. I should have
substantially more time after the new year begins.
- Ted
next prev parent reply other threads:[~2007-11-12 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071106113142.GA23689@duck.suse.cz>
2007-11-07 16:09 ` [PATCH] e2fsprogs: Handle rec_len correctly for 64KB blocksize Jan Kara
2007-11-11 0:37 ` Theodore Tso
2007-11-12 9:52 ` Jan Kara
2007-11-12 14:58 ` Theodore Tso [this message]
2007-11-12 16:10 ` Jan Kara
2007-11-13 15:08 ` Andreas Dilger
2007-12-06 14:11 Jan Kara
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=20071112145823.GB17462@thunk.org \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.