From: "Theodore Ts'o" <tytso@mit.edu>
To: Kirill Tkhai <ktkhai@virtuozzo.com>
Cc: jack@suse.cz, adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Actually request zeroing of inode table after grow
Date: Thu, 25 Apr 2019 13:23:47 -0400 [thread overview]
Message-ID: <20190425172347.GD4739@mit.edu> (raw)
In-Reply-To: <155592139208.19009.5887870564232862529.stgit@localhost.localdomain>
On Mon, Apr 22, 2019 at 11:23:20AM +0300, Kirill Tkhai wrote:
> It is never possible, that number of block groups decreases,
> since only online grow is supported.
>
> But after a growing occured, we have to zero inode tables
> for just created new block groups.
>
> Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
> Reviewed-by: Jan Kara <jack@suse.cz>
Applied, thanks.
- Ted
prev parent reply other threads:[~2019-04-25 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 8:23 [PATCH] ext4: Actually request zeroing of inode table after grow Kirill Tkhai
2019-04-25 17:23 ` Theodore Ts'o [this message]
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=20190425172347.GD4739@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=ktkhai@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).