From: Jeff Liu <jeff.liu@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: fix BUG_ON issue in ocfs2_set_new_buffer_uptodate
Date: Fri, 09 Nov 2012 13:22:00 +0800 [thread overview]
Message-ID: <509C92F8.5020703@oracle.com> (raw)
In-Reply-To: <1352436228-18544-1-git-send-email-tiger.yang@oracle.com>
On 11/09/2012 12:43 PM, Tiger Yang wrote:
> If buffer already in cache, call ocfs2_init_xattr_bucket will cause BUG_ON
> in ocfs2_set_new_buffer_uptodate. The check of ocfs2_buffer_uptodate
> in ocfs2_init_xattr_bucket wouldn't help this. So replace it with
> ocfs2_read_xattr_bucket to initialize the bucket to avoid this issue.
>
> Signed-off-by: Tiger Yang <tiger.yang@oracle.com>
> ---
> fs/ocfs2/xattr.c | 12 ++----------
> 1 files changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/fs/ocfs2/xattr.c b/fs/ocfs2/xattr.c
> index dce35dd..0085261 100644
> --- a/fs/ocfs2/xattr.c
> +++ b/fs/ocfs2/xattr.c
> @@ -4640,11 +4640,7 @@ static int ocfs2_divide_xattr_bucket(struct inode *inode,
> goto out;
> }
>
> - /*
> - * Even if !new_bucket_head, we're overwriting t_bucket. Thus,
> - * there's no need to read it.
> - */
> - ret = ocfs2_init_xattr_bucket(t_bucket, new_blk);
> + ret = ocfs2_read_xattr_bucket(t_bucket, new_blk);
> if (ret) {
> mlog_errno(ret);
> goto out;
> @@ -4806,11 +4802,7 @@ static int ocfs2_cp_xattr_bucket(struct inode *inode,
> if (ret)
> goto out;
>
> - /*
> - * Even if !t_is_new, we're overwriting t_bucket. Thus,
> - * there's no need to read it.
> - */
> - ret = ocfs2_init_xattr_bucket(t_bucket, t_blkno);
> + ret = ocfs2_read_xattr_bucket(t_bucket, t_blkno);
> if (ret)
> goto out;
>
Looks good to me.
You can add a Reviewed-by: Jie Liu <jeff.liu@oracle.com>
Thanks,
-Jeff
prev parent reply other threads:[~2012-11-09 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 4:43 [Ocfs2-devel] [PATCH] ocfs2: fix BUG_ON issue in ocfs2_set_new_buffer_uptodate Tiger Yang
2012-11-09 5:22 ` Jeff Liu [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=509C92F8.5020703@oracle.com \
--to=jeff.liu@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.