From: Theodore Tso <tytso@mit.edu>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: cmm@us.ibm.com, sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Don't reuse released data blocks untill transaction commits
Date: Sun, 12 Oct 2008 16:33:27 -0400 [thread overview]
Message-ID: <20081012203327.GG12662@mit.edu> (raw)
In-Reply-To: <1223566329-29434-2-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
On Thu, Oct 09, 2008 at 09:02:08PM +0530, Aneesh Kumar K.V wrote:
> We need to make sure we don't reuse the data blocks released
> during the transaction untill the transaction commits. We force
> this mode only for ordered and journalled mode. Writeback mode
> already don't provided data consistency.
It might be a good idea in ext4_free_mb_metadata() to add a comment
that the name of the function is a little bit of a misnomer...
BTW, you may want to check what I put in the patch queue, because
iirc, I fixed up a few spelling/grammar in the patch comments.
- Ted
next prev parent reply other threads:[~2008-10-12 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 15:32 [PATCH] ext4: Use an rb tree for tracking blocks freed during transaction Aneesh Kumar K.V
2008-10-09 15:32 ` [PATCH] ext4: Don't reuse released data blocks untill transaction commits Aneesh Kumar K.V
2008-10-09 15:32 ` [PATCH] ext4: Do mballoc init before doing filesystem recovery Aneesh Kumar K.V
2008-10-12 20:33 ` Theodore Tso [this message]
2008-10-11 4:27 ` [PATCH] ext4: Use an rb tree for tracking blocks freed during transaction Theodore Tso
2008-10-11 18:08 ` Aneesh Kumar K.V
2008-10-12 20:31 ` Theodore Tso
2008-10-13 9:46 ` Aneesh Kumar K.V
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=20081012203327.GG12662@mit.edu \
--to=tytso@mit.edu \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).