From: Theodore Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org, wenqing.lz@taobao.com
Subject: Re: [PATCH] ext4: use s_extent_max_zeroout_kb value as number of kb
Date: Tue, 12 Mar 2013 12:45:11 -0400 [thread overview]
Message-ID: <20130312164511.GC4959@thunk.org> (raw)
In-Reply-To: <1363106209-1883-1-git-send-email-lczerner@redhat.com>
Thanks, applied.
I'm on the fence about whether to submit this after -rc2 or not.
This appears to make potential bug much rarer, and it's a trivial
patch to backport, but it does make rather large changes in how we
handle fragmented filesystem. (For the better, but it's a large
change, and it is getting rather late in the season.)
I'm going to include in the dev branch for now, and give it all a good
instensive testing, but there may be some patches in dev that may get
deferred to the next merge window before I send a pull request to
Linus (probably during the coming weekend).
Folks should feel free to propose patches they think should wait for
the next merge window.
- Ted
next prev parent reply other threads:[~2013-03-12 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 16:36 [PATCH] ext4: use s_extent_max_zeroout_kb value as number of kb Lukas Czerner
2013-03-12 16:45 ` Theodore Ts'o [this message]
2013-03-13 6:53 ` Lukáš Czerner
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=20130312164511.GC4959@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=wenqing.lz@taobao.com \
/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