From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2/trivial: Use le16_to_cpu for a disk value in xattr.c
Date: Wed, 23 Dec 2009 10:48:04 -0800 [thread overview]
Message-ID: <4B3265E4.9060000@oracle.com> (raw)
In-Reply-To: <1261549875-14192-1-git-send-email-tao.ma@oracle.com>
Ack.
Tao Ma wrote:
> In ocfs2_value_metas_in_xattr_header, we should Use
> le16_to_cpu for ocfs2_extent_list.l_next_free_rec.
>
> Signed-off-by: Tao Ma <tao.ma@oracle.com>
> ---
> fs/ocfs2/xattr.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ocfs2/xattr.c b/fs/ocfs2/xattr.c
> index fe34190..8c0bfa2 100644
> --- a/fs/ocfs2/xattr.c
> +++ b/fs/ocfs2/xattr.c
> @@ -6066,7 +6066,7 @@ static int ocfs2_value_metas_in_xattr_header(struct super_block *sb,
> * to the extent block, so just calculate a maximum record num.
> */
> if (!xv->xr_list.l_tree_depth)
> - *num_recs += xv->xr_list.l_next_free_rec;
> + *num_recs += le16_to_cpu(xv->xr_list.l_next_free_rec);
> else
> *num_recs += ocfs2_clusters_for_bytes(sb,
> XATTR_SIZE_MAX);
>
prev parent reply other threads:[~2009-12-23 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 6:31 [Ocfs2-devel] [PATCH] ocfs2/trivial: Use le16_to_cpu for a disk value in xattr.c Tao Ma
2009-12-23 18:48 ` Sunil Mushran [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=4B3265E4.9060000@oracle.com \
--to=sunil.mushran@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.