From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/4] ocfs2: use allocation reservations during file write
Date: Tue, 16 Mar 2010 17:19:25 +0800 [thread overview]
Message-ID: <4B9F4D1D.7010009@oracle.com> (raw)
In-Reply-To: <1268188148-5253-3-git-send-email-mfasheh@suse.com>
Hi Mark,
Mark Fasheh wrote:
> Add a per-inode reservations structure and pass it through to the
> reservations code.
>
> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
> ---
> fs/ocfs2/alloc.c | 2 ++
> fs/ocfs2/aops.c | 2 ++
> fs/ocfs2/file.c | 3 +++
> fs/ocfs2/inode.c | 4 ++++
> fs/ocfs2/inode.h | 2 ++
> fs/ocfs2/super.c | 2 ++
> 6 files changed, 15 insertions(+), 0 deletions(-)
<snip>
>
> diff --git a/fs/ocfs2/aops.c b/fs/ocfs2/aops.c
> index 7e9df11..137d460 100644
> --- a/fs/ocfs2/aops.c
> +++ b/fs/ocfs2/aops.c
> @@ -1734,6 +1734,8 @@ int ocfs2_write_begin_nolock(struct address_space *mapping,
> goto out;
> }
>
> + data_ac->ac_resv = &OCFS2_I(inode)->ip_la_data_resv;
> +
Here is a bug. In case, we are writing the unwritten extents, we don't
have a valid data_ac.
> credits = ocfs2_calc_extend_credits(inode->i_sb,
> &di->id2.i_list,
> clusters_to_alloc);
Regards,
Tao
next prev parent reply other threads:[~2010-03-16 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 2:29 [Ocfs2-devel] [PATCH 0/4] Ocfs2 allocation reservations Mark Fasheh
2010-03-10 2:29 ` [Ocfs2-devel] [PATCH 1/4] ocfs2: " Mark Fasheh
2010-03-16 9:17 ` Tao Ma
2010-03-17 3:13 ` Mark Fasheh
2010-03-17 3:32 ` Tao Ma
2010-03-10 2:29 ` [Ocfs2-devel] [PATCH 2/4] ocfs2: use allocation reservations during file write Mark Fasheh
2010-03-16 9:19 ` Tao Ma [this message]
2010-03-10 2:29 ` [Ocfs2-devel] [PATCH 3/4] ocfs2: use allocation reservations for directory data Mark Fasheh
2010-03-10 2:29 ` [Ocfs2-devel] [PATCH 4/4] ocfs2: allocate btree internal block groups from the global bitmap Mark Fasheh
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=4B9F4D1D.7010009@oracle.com \
--to=tao.ma@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.