From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Kees Cook <keescook@chromium.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org,
Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH][next] xfs: Replace one-element arrays with flexible-array members
Date: Mon, 6 Feb 2023 13:17:14 -0600 [thread overview]
Message-ID: <f6bec0de-3d6d-6d59-5ef3-2903f40451d3@embeddedor.com> (raw)
In-Reply-To: <63dd4a37.630a0220.e4652.35de@mx.google.com>
On 2/3/23 11:53, Kees Cook wrote:
> On Thu, Feb 02, 2023 at 07:24:50PM -0600, Gustavo A. R. Silva wrote:
>> One-element arrays are deprecated, and we are replacing them with flexible
>> array members instead. So, replace one-element arrays with flexible-array
>> members in structures xfs_attr_leaf_name_local and
>> xfs_attr_leaf_name_remote.
>>
>> The only binary differences reported after the changes are all like
>> these:
>>
>> fs/xfs/libxfs/xfs_attr_leaf.o
>> _@@ -435,7 +435,7 @@
>> 3b8: movzbl 0x2(%rbx),%eax
>> 3bc: rol $0x8,%bp
>> 3c0: movzwl %bp,%ebp
>> - 3c3: lea 0x2(%rax,%rbp,1),%ebx
>> + 3c3: lea 0x3(%rax,%rbp,1),%ebx
>> 3c7: call 3cc <xfs_attr_leaf_entsize+0x8c>
>> 3c8: R_X86_64_PLT32 __tsan_func_exit-0x4
>> 3cc: or $0x3,%ebx
>> _@@ -454,7 +454,7 @@
>> 3ea: movzbl 0x8(%rbx),%ebx
>> 3ee: call 3f3 <xfs_attr_leaf_entsize+0xb3>
>> 3ef: R_X86_64_PLT32 __tsan_func_exit-0x4
>> - 3f3: add $0xa,%ebx
>> + 3f3: add $0xb,%ebx
>> 3f6: or $0x3,%ebx
>> 3f9: add $0x1,%ebx
>> 3fc: mov %ebx,%eax
>>
>> similar changes in fs/xfs/scrub/attr.o and fs/xfs/xfs.o object files.
>
> I usually turn off the sanitizers for the A/B build comparisons to make
Oh yes! that's a good point. I'll see that they are turned off next time. :)
> it easier to read the results. It looks like it _grew_ in size here,
> though?
Yep; I'm sorry I got it wrong. :/ I had it right in the beginning, then after
reading the code once again just before sending out a version of this patch
with only the flex-array transformations, I noticed the entsize functions and
the "sizeof(struct-with-one-element-array) - 1" and I forgot about the padding,
removed the "- 1" and got a bit confused with my build-tests.
I'll send v2 with my original changes... the flex-array transformations, only.
--
Gustavo
next prev parent reply other threads:[~2023-02-06 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 1:24 [PATCH][next] xfs: Replace one-element arrays with flexible-array members Gustavo A. R. Silva
2023-02-03 17:53 ` Kees Cook
2023-02-06 19:17 ` Gustavo A. R. Silva [this message]
2023-02-03 21:32 ` Darrick J. Wong
2023-02-05 22:51 ` Dave Chinner
2023-02-06 0:21 ` Gustavo A. R. Silva
-- strict thread matches above, loose matches on Subject: below --
2021-03-02 15:05 Gustavo A. R. Silva
2021-03-09 17:42 ` Darrick J. Wong
2021-03-09 19:57 ` Gustavo A. R. Silva
2021-03-09 21:26 ` Darrick J. Wong
2021-03-09 22:03 ` Gustavo A. R. Silva
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=f6bec0de-3d6d-6d59-5ef3-2903f40451d3@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).