From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Use cpu_to_le16 for e_leaf_clusters in ocfs2_bg_discontig_add_extent.
Date: Sun, 12 Sep 2010 23:29:08 -0700 [thread overview]
Message-ID: <20100913062907.GA16449@mail.oracle.com> (raw)
In-Reply-To: <1284358193-3222-1-git-send-email-tao.ma@oracle.com>
On Mon, Sep 13, 2010 at 02:09:53PM +0800, Tao Ma wrote:
> e_leaf_clusters is a le16, so use cpu_to_le16 instead
> of cpu_to_le32.
>
> Signed-off-by: Tao Ma <tao.ma@oracle.com>
You're right that we need to swap as an le16.
> @@ -348,7 +348,7 @@ static void ocfs2_bg_discontig_add_extent(struct ocfs2_super *osb,
> rec->e_blkno = cpu_to_le64(p_blkno);
> rec->e_cpos = cpu_to_le32(le16_to_cpu(bg->bg_bits) /
> le16_to_cpu(cl->cl_bpc));
> - rec->e_leaf_clusters = cpu_to_le32(clusters);
> + rec->e_leaf_clusters = cpu_to_le16(clusters);
For a second I was worried, "what about overflow if clusters >
16bits?" Of course, this is coming from discontig stuff which starts at
cpg, so it can't overflow. Maybe discontig_add_extent should take
"unsigned int clusters" instead of "u32 clusters" to signify that the
size of 'clusters isn't important here?
Joel
--
"Friends may come and go, but enemies accumulate."
- Thomas Jones
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-09-13 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 6:09 [Ocfs2-devel] [PATCH] ocfs2: Use cpu_to_le16 for e_leaf_clusters in ocfs2_bg_discontig_add_extent Tao Ma
2010-09-13 6:29 ` Joel Becker [this message]
2010-09-13 7:13 ` [Ocfs2-devel] [PATCH v2] " Tao Ma
2010-09-23 21:23 ` Joel Becker
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=20100913062907.GA16449@mail.oracle.com \
--to=joel.becker@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).