From: Eric Biggers <ebiggers@kernel.org>
To: "zhangjianhua (E)" <chris.zjh@huawei.com>
Cc: tytso@mit.edu, linux-fscrypt@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next v2] fs-verity: Use struct_size() helper in enable_verity()
Date: Wed, 18 May 2022 21:22:41 -0700 [thread overview]
Message-ID: <YoXGEckfSNWKj2oT@sol.localdomain> (raw)
In-Reply-To: <e030eaf6-0b6b-7685-c5b6-fd0b57aea600@huawei.com>
[Please use reply all, not just reply!]
On Thu, May 19, 2022 at 11:54:48AM +0800, zhangjianhua (E) wrote:
> Hi Eric
>
> The warnings in commit message are from the build log in Jan 2022, and I
> find these sizeof are still here, so I submit
>
> these two patches. I build the kernel just now and encounter the same
> situation with you, there are lots of warnings.
>
> Maybe you are right, there should be some mechanism to solve this problem
> completely.
>
>
I've updated the commit message and applied this patch, but not the other one,
as the other one wasn't actually dealing with a variable length which made it
pretty much pointless, as I mentioned.
If you'd like to look into making sparse enable this warning by default, I'd
certainly encourage you to do so. But it looks like the warning itself could
use some more work. It probably should only warn if the
sizeof(struct_with_flexible_array) is actually being added to another value, and
where that value is not a compile-time constant.
- Eric
next prev parent reply other threads:[~2022-05-19 4:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 2:24 [PATCH -next v2] fs-verity: Use struct_size() helper in enable_verity() Zhang Jianhua
2022-05-19 3:06 ` Eric Biggers
2022-05-19 3:17 ` Eric Biggers
[not found] ` <e030eaf6-0b6b-7685-c5b6-fd0b57aea600@huawei.com>
2022-05-19 4:22 ` Eric Biggers [this message]
2022-05-19 6:22 ` zhangjianhua (E)
2022-05-19 11:24 ` Johan Hovold
2022-05-19 16:57 ` Eric Biggers
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=YoXGEckfSNWKj2oT@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=chris.zjh@huawei.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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