From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] Ocfs2: __ocfs2_find_path() needs to treat hole correctly.
Date: Fri, 26 Mar 2010 07:36:56 +0800 [thread overview]
Message-ID: <4BABF398.4040706@oracle.com> (raw)
In-Reply-To: <1269506159-30981-1-git-send-email-tristan.ye@oracle.com>
Tristan Ye wrote:
> Currently, __ocfs2_find_path() was lack of a mechanism to detect
> a hole between two extent blocks if the cpos we want to search is
> within the hole, as a result, the last rec will be returned incorrectly.
>
Do you mean extent block or extent rec? The extent block are contiguous
and there should be no hole.
oh, here. We should never meet with this. So Nack.
Regards,
Tao
>
> This patch attempts to detect a hole, and return the rightmost
> extent block preceding the hole.
>
> Signed-off-by: Tristan Ye <tristan.ye@oracle.com>
> ---
> fs/ocfs2/alloc.c | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/fs/ocfs2/alloc.c b/fs/ocfs2/alloc.c
> index 9f8bd91..2638a18 100644
> --- a/fs/ocfs2/alloc.c
> +++ b/fs/ocfs2/alloc.c
> @@ -1841,6 +1841,17 @@ static int __ocfs2_find_path(struct ocfs2_caching_info *ci,
> ocfs2_rec_clusters(el, rec);
> if (cpos >= le32_to_cpu(rec->e_cpos) && cpos < range)
> break;
> +
> + /*
> + * Return the rightmost extent block leftly adjacent
> + * to a hole if there is any between two extent blocks.
> + *
> + * Otherwise, we get the last rec of this block unexpectly.
> + */
> + if (cpos < le32_to_cpu(rec->e_cpos)) {
> + i--;
> + break;
> + }
> }
>
> blkno = le64_to_cpu(el->l_recs[i].e_blkno);
>
next prev parent reply other threads:[~2010-03-25 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 8:35 [Ocfs2-devel] [PATCH 1/1] Ocfs2: __ocfs2_find_path() needs to treat hole correctly Tristan Ye
2010-03-25 23:36 ` Tao Ma [this message]
2010-03-26 1:25 ` tristan
2010-03-26 1:26 ` Tao Ma
2010-03-26 1:32 ` tristan
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=4BABF398.4040706@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.