From: Joel Becker <jlbec@evilplan.org>
To: yili <yili@winhong.com>
Cc: joseph.qi@linux.alibaba.com, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ocfs2: Fix super block reserved field offset comment
Date: Thu, 7 Aug 2025 12:23:50 -0700 [thread overview]
Message-ID: <aJT9RpG19PWIcLe-@google.com> (raw)
In-Reply-To: <20250807155749.164481-1-yili@winhong.com>
Yep. And 140 - (sizeof(s_reserved2) aka 8 * F) = C8.
Reviewed-by: Joel Becker <jlbec@evilplan.org>
On Thu, Aug 07, 2025 at 11:57:49PM +0800, yili wrote:
> The offset annotation for s_reserved2 in struct ocfs2_super_block
> was incorrect. After the preceding fields:
> - s_xattr_inline_size (2 bytes at 0xB8)
> - s_reserved0 (2 bytes at 0xBA)
> - s_dx_seed[3] (12 bytes at 0xBC)
>
> The actual offset of s_reserved2 is at 0xC8,
> when calculating from the start of the structure.
>
> Correct the offset comment from C0 to C8 to reflect the proper
> location in the super block structure.
>
> Signed-off-by: yili <yili@winhong.com>
> ---
> fs/ocfs2/ocfs2_fs.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/ocfs2_fs.h b/fs/ocfs2/ocfs2_fs.h
> index e8e94599e907..ae0e44e5f2ad 100644
> --- a/fs/ocfs2/ocfs2_fs.h
> +++ b/fs/ocfs2/ocfs2_fs.h
> @@ -614,7 +614,7 @@ struct ocfs2_super_block {
> __le16 s_reserved0;
> __le32 s_dx_seed[3]; /* seed[0-2] for dx dir hash.
> * s_uuid_hash serves as seed[3]. */
> -/*C0*/ __le64 s_reserved2[15]; /* Fill out superblock */
> +/*C8*/ __le64 s_reserved2[15]; /* Fill out superblock */
> /*140*/
>
> /*
> --
> 2.43.0
>
--
Life's Little Instruction Book #15
"Own a great stereo system."
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2025-08-07 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 15:57 [PATCH] ocfs2: Fix super block reserved field offset comment yili
2025-08-07 19:23 ` Joel Becker [this message]
2025-08-22 1:16 ` Joseph Qi
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=aJT9RpG19PWIcLe-@google.com \
--to=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=yili@winhong.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).