From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: yili <yili@winhong.com>, akpm <akpm@linux-foundation.org>
Cc: Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
"ocfs2-devel@lists.linux.dev" <ocfs2-devel@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ocfs2: Fix super block reserved field offset comment
Date: Fri, 22 Aug 2025 09:16:58 +0800 [thread overview]
Message-ID: <e7adfc92-6c0d-4fc6-8e73-5c1acd61753c@linux.alibaba.com> (raw)
In-Reply-To: <aJT9RpG19PWIcLe-@google.com>
On 2025/8/8 03:23, Joel Becker wrote:
> Yep. And 140 - (sizeof(s_reserved2) aka 8 * F) = C8.
>
> Reviewed-by: Joel Becker <jlbec@evilplan.org>
>
Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> 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
>>
>
prev parent reply other threads:[~2025-08-22 1:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 15:57 yili
2025-08-07 19:23 ` Joel Becker
2025-08-22 1:16 ` Joseph Qi [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=e7adfc92-6c0d-4fc6-8e73-5c1acd61753c@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--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
all inboxes | Powered by JetHome®