From: Chao Yu <chao2.yu@samsung.com>
To: 'Sheng Yong' <shengyong1@huawei.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: fix endianness of on-disk summary_footer
Date: Thu, 28 Jan 2016 16:31:57 +0800 [thread overview]
Message-ID: <00f401d159a6$72523b50$56f6b1f0$@samsung.com> (raw)
In-Reply-To: <1453981226-18858-1-git-send-email-shengyong1@huawei.com>
Hi Sheng,
> -----Original Message-----
> From: Sheng Yong [mailto:shengyong1@huawei.com]
> Sent: Thursday, January 28, 2016 7:40 PM
> To: jaegeuk@kernel.org
> Cc: chao2.yu@samsung.com; linux-f2fs-devel@lists.sourceforge.net; shengyong1@huawei.com
> Subject: [PATCH] f2fs: fix endianness of on-disk summary_footer
>
> Signed-off-by: Sheng Yong <shengyong1@huawei.com>
Nice catch!
Reviewed-by: Chao Yu <chao2.yu@samsung.com>
Thanks,
> ---
> include/linux/f2fs_fs.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/f2fs_fs.h b/include/linux/f2fs_fs.h
> index 25c6324..2863274 100644
> --- a/include/linux/f2fs_fs.h
> +++ b/include/linux/f2fs_fs.h
> @@ -344,7 +344,7 @@ struct f2fs_summary {
>
> struct summary_footer {
> unsigned char entry_type; /* SUM_TYPE_XXX */
> - __u32 check_sum; /* summary checksum */
> + __le32 check_sum; /* summary checksum */
> } __packed;
>
> #define SUM_JOURNAL_SIZE (F2FS_BLKSIZE - SUM_FOOTER_SIZE -\
> --
> 1.9.1
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
prev parent reply other threads:[~2016-01-28 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 11:40 [PATCH] f2fs: fix endianness of on-disk summary_footer Sheng Yong
2016-01-28 8:31 ` Chao Yu [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='00f401d159a6$72523b50$56f6b1f0$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=shengyong1@huawei.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).