From: Eric Sandeen <sandeen@redhat.com>
To: Lukas Czerner <lczerner@redhat.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
linux-ext4@vger.kernel.org, tytso@mit.edu, psusi@ubuntu.com
Subject: Re: [PATCH 1/2 v2] e2fsck: Discard only unused parts of inode table
Date: Thu, 01 Mar 2012 11:35:59 -0600 [thread overview]
Message-ID: <4F4FB37F.60405@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1202290812530.4926@dhcp-27-109.brq.redhat.com>
On 2/29/12 1:22 AM, Lukas Czerner wrote:
> On Tue, 28 Feb 2012, Eric Sandeen wrote:
...
>>> + /*
>>> + * If the last inode is free, we can discard it as well.
>>> + */
>>> + if (inodes >= first_free)
>>> + e2fsck_discard_inodes(ctx, group, first_free,
>>> + inodes - first_free + 1);
>>
>> This is unrelated to the changelog
>>
>>> /*
>>> * If discard zeroes data and the group inode table
>>> * was not zeroed yet, set itable as zeroed
>>> */
>>> if ((ctx->options & E2F_OPT_DISCARD) &&
>>> - (io_channel_discard_zeroes_data(fs->io)) &&
>>> + !(ctx->options & E2F_OPT_NO) &&
>>
>> This is unrelated as well...
>
> So do you want me to separate those unrelated changes to a separate
> patch ? Those are pretty small changes..
They are, but they are completely separate fixes, and not described in the changelog.
Ideally I'd say they should be a separate testable commit, but at least it
should be mentioned in the changelog (and patch summary).
Sorry, compound commits with unrelated changes are my pet peeve; they make bisecting
harder, and make it harder to find fixes when looking back over git history.
-Eric
>>
>> Rather than continuing to check _OPT_NO here and in e2fsck_discard_blocks(), it
>> might be better (in a separate patch) ;) to simply turn off OPT_DISCARD right
>> after options processing if -n was specified, and not worry about it down here.
>
> Makes sense, I can change it.
>
> Thanks!
> -Lukas
>
>>
>>> + io_channel_discard_zeroes_data(fs->io) &&
>>> !(ext2fs_bg_flags_test(fs, group,
>>> - EXT2_BG_INODE_ZEROED))) {
>>> + EXT2_BG_INODE_ZEROED))) {
>>> ext2fs_bg_flags_set(fs, group,
>>> EXT2_BG_INODE_ZEROED);
>>> ext2fs_group_desc_csum_set(fs, group);
>>> }
>>>
>>> + first_free = fs->super->s_inodes_per_group + 1;
>>> + free_array[group] = group_free;
>>> + dir_array[group] = dirs_count;
>>> group ++;
>>> inodes = 0;
>>> skip_group = 0;
>>
>>
>
next prev parent reply other threads:[~2012-03-01 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 16:29 [PATCH 1/2 v2] e2fsck: Discard only unused parts of inode table Lukas Czerner
2012-02-27 5:42 ` Ted Ts'o
2012-02-27 7:03 ` Lukas Czerner
2012-02-28 16:31 ` Eric Sandeen
2012-02-29 7:22 ` Lukas Czerner
2012-03-01 17:35 ` Eric Sandeen [this message]
2012-03-06 22:22 ` Ted Ts'o
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=4F4FB37F.60405@redhat.com \
--to=sandeen@redhat.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=psusi@ubuntu.com \
--cc=sandeen@sandeen.net \
--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 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.