ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Srinivas Eeda <srinivas.eeda@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] allow for more than one data extent when creating xattr
Date: Mon, 10 Mar 2014 14:59:52 -0700	[thread overview]
Message-ID: <531E35D8.6020102@oracle.com> (raw)
In-Reply-To: <1394485700-12641-1-git-send-email-tariq.x.saeed@oracle.com>

looks good to me.
Reviewed-by: Srinivas Eeda <srinivas.eeda@oracle.com>

On 03/10/2014 02:08 PM, Tariq Saeed wrote:
> Orabug: 18108070
>
> ocfs2_xattr_extend_allocation() hits panic when creating xattr during
> data extent alloc phase. The problem occurs if due to local alloc
> fragmentation, clusters are spread over multiple extents.  In this case
> ocfs2_add_clusters_in_btree() finds no space to store more than one extent
> record and therefore fails returning RESTART_META.  The situation is
> anticipated for xattr update case but not xattr create case. This fix
> simply ports that code to create case.
>
> Signed-off-by: Tariq Saeed <tariq.x.saeed@oracle.com>
> ---
>   fs/ocfs2/xattr.c |    9 ++++++++-
>   1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ocfs2/xattr.c b/fs/ocfs2/xattr.c
> index 5b8d944..bfa1c37 100644
> --- a/fs/ocfs2/xattr.c
> +++ b/fs/ocfs2/xattr.c
> @@ -3207,8 +3207,15 @@ meta_guess:
>   			clusters_add += 1;
>   		}
>   	} else {
> -		meta_add += 1;
>   		credits += OCFS2_XATTR_BLOCK_CREATE_CREDITS;
> +		if (xi->xi_value_len > OCFS2_XATTR_INLINE_SIZE) {
> +			struct ocfs2_extent_list *el = &def_xv.xv.xr_list;
> +			meta_add += ocfs2_extend_meta_needed(el);
> +			credits += ocfs2_calc_extend_credits(inode->i_sb,
> +							     el, 1);
> +		} else {
> +			meta_add += 1;
> +		}
>   	}
>   out:
>   	if (clusters_need)

  reply	other threads:[~2014-03-10 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 21:08 [Ocfs2-devel] [PATCH] allow for more than one data extent when creating xattr Tariq Saeed
2014-03-10 21:59 ` Srinivas Eeda [this message]
2014-03-12 21:37 ` Andrew Morton

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=531E35D8.6020102@oracle.com \
    --to=srinivas.eeda@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).