From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Make ocfs2_extend_trans really extending.
Date: Sun, 25 Apr 2010 23:54:26 -0700 [thread overview]
Message-ID: <20100426065424.GA17377@mail.oracle.com> (raw)
In-Reply-To: <1272263697-5701-1-git-send-email-tao.ma@oracle.com>
On Mon, Apr 26, 2010 at 02:34:57PM +0800, Tao Ma wrote:
> >From c9dc26549b429eede9e47094a98b067bd5cd23b1 Mon Sep 17 00:00:00 2001
> From: Tao Ma <tao.ma@oracle.com>
> Date: Mon, 26 Apr 2010 13:49:11 +0800
> Subject: [PATCH] ocfs2: Make ocfs2_extend_trans really extending.
>
> In ocfs2, we use ocfs2_extend_trans to extend a journal's
> blocks. But it is designed that in case jbd2_journal_extend
> fails, it will only restart with the the new block number.
> This tends to be awkward since in most cases we want our
> original reserved blocks there and make our codes hard to
> mantain since the caller sometimes can't make sure all the
> original blocks will not be accessed and dirtied again.
> There are 15 callers of ocfs2_extend_trans in fs/ocfs2,
> and 12 of them have to add h_buffer_credits before they
> call ocfs2_extend_trans. So make it really behaves like
> extending.
>
> Signed-off-by: Tao Ma <tao.ma@oracle.com>
This is now in the 'merge-window' branch of ocfs2.git.
Joel
--
"Hey mister if you're gonna walk on water,
Could you drop a line my way?"
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
prev parent reply other threads:[~2010-04-26 6:54 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
2010-04-26 6:34 ` [Ocfs2-devel] [PATCH] " Tao Ma
2010-04-26 6:54 ` Joel Becker [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=20100426065424.GA17377@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).