From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC] ocfs2: Make ocfs2_extend_trans really extending.
Date: Fri, 23 Apr 2010 13:45:45 -0700 [thread overview]
Message-ID: <20100423204545.GB10637@mail.oracle.com> (raw)
In-Reply-To: <1271820579-29614-1-git-send-email-tao.ma@oracle.com>
On Wed, Apr 21, 2010 at 11:29:39AM +0800, Tao Ma wrote:
> I have finished the tests on xattr and reflink(I use reflink for b-tree
> test because it also use b-tree heavily and also it has a stress test
> case which create a b-tree with depth=2 easily). Both test cases works.
> So please consider including it in the merge window. Thanks.
I think I'm happy to take this patch, but a couple things first.
> I also changed the patch a little in the beginning of ocfs2_extend_trans.
> - BUG_ON(!nblocks);
> + if (nblocks <= 0)
> + return 0;
> +
> The reason is that some b-tree codes now will extend transcation with
> tree depth. So sometimes it may give us a '0' and we will just return back.
Well, negative nblocks is still a bug, right? shouldn't we at
least warn or make it an unsigned int?
Joel
--
"In a crisis, don't hide behind anything or anybody. They're going
to find you anyway."
- Paul "Bear" Bryant
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-04-23 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 8:01 [Ocfs2-devel] [RFC] ocfs2: Make ocfs2_extend_trans really extending Tao Ma
2010-04-07 21:53 ` Mark Fasheh
2010-04-07 23:43 ` Tao Ma
2010-04-07 23:54 ` Joel Becker
2010-04-21 3:29 ` Tao Ma
2010-04-23 20:45 ` Joel Becker [this message]
2010-04-26 6:34 ` [Ocfs2-devel] [PATCH] " Tao Ma
2010-04-26 6:54 ` Joel Becker
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=20100423204545.GB10637@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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).