From: Eric Biggers <ebiggers@kernel.org>
To: Zhang Jianhua <chris.zjh@huawei.com>
Cc: tytso@mit.edu, linux-fscrypt@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] fs-verity: Use struct_size() helper in enable_verity()
Date: Wed, 18 May 2022 10:55:34 -0700 [thread overview]
Message-ID: <YoUzFm9kL13oQi0K@sol.localdomain> (raw)
In-Reply-To: <20220518061309.2179692-1-chris.zjh@huawei.com>
On Wed, May 18, 2022 at 02:13:09PM +0800, Zhang Jianhua wrote:
> Make use of the struct_size() helper instead of an open-coded version,
> in order to avoid any potential type mistakes or integer overflows
> that, in the worst scenario, could lead to heap overflows.
>
> Also, address the following sparse warnings:
> fs/verity/enable.c:205:28: warning: using sizeof on a flexible structure
>
> Signed-off-by: Zhang Jianhua <chris.zjh@huawei.com>
> ---
> fs/verity/enable.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/verity/enable.c b/fs/verity/enable.c
> index f75d2c010f36..075dc0aa5416 100644
> --- a/fs/verity/enable.c
> +++ b/fs/verity/enable.c
> @@ -201,7 +201,7 @@ static int enable_verity(struct file *filp,
> const struct fsverity_operations *vops = inode->i_sb->s_vop;
> struct merkle_tree_params params = { };
> struct fsverity_descriptor *desc;
> - size_t desc_size = sizeof(*desc) + arg->sig_size;
> + size_t desc_size = struct_size(desc, signature, arg->sig_size);
> struct fsverity_info *vi;
> int err;
This patch is a bit more useful than the other one, as the validation of
->sig_size happens in a different function. But it still happens. So please
don't claim that this patch is fixing a heap overflow. People use commit
messages to determine whether patches are fixing something, and how important
the fix is. So if it's a cleanup (not a bug fix), write that.
- Eric
prev parent reply other threads:[~2022-05-18 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 6:13 [PATCH -next] fs-verity: Use struct_size() helper in enable_verity() Zhang Jianhua
2022-05-18 17:55 ` Eric Biggers [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=YoUzFm9kL13oQi0K@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