From: Kees Cook <keescook@chromium.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: arno@natisbad.org, arnd@kernel.org, schalla@marvell.com,
bbrezillon@kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: marvell/cesa - Fix type mismatch warning
Date: Wed, 31 May 2023 09:31:18 -0700 [thread overview]
Message-ID: <202305310930.844EBEA21C@keescook> (raw)
In-Reply-To: <ZHcoQvWnzO0c1Cp9@gondor.apana.org.au>
On Wed, May 31, 2023 at 06:58:10PM +0800, Herbert Xu wrote:
> On Tue, May 30, 2023 at 03:48:49PM -0700, Kees Cook wrote:
> > On Tue, 23 May 2023 10:33:04 +0200, Arnd Bergmann wrote:
> > > From: Arnd Bergmann <arnd@arndb.de>
> > >
> > > Commit df8fc4e934c1 ("kbuild: Enable -fstrict-flex-arrays=3") uncovered
> > > a type mismatch in cesa 3des support that leads to a memcpy beyond the
> > > end of a structure:
> > >
> > > In function 'fortify_memcpy_chk',
> > > inlined from 'mv_cesa_des3_ede_setkey' at drivers/crypto/marvell/cesa/cipher.c:307:2:
> > > include/linux/fortify-string.h:583:25: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]
> > > 583 | __write_overflow_field(p_size_field, size);
> > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > >
> > > [...]
> >
> > Applied to for-next/hardening, thanks!
> >
> > [1/1] crypto: marvell/cesa - Fix type mismatch warning
> > https://git.kernel.org/kees/c/37f3abddda8d
>
> Why did you apply it to your tree? This patch makes sense on its
> own regardless of the fortify changes.
I snagged it since a week had gone by with no additional discussion and
it fixed an issue exposed by work in the hardening tree. Let me know if
you'd prefer I drop it for you to carry instead.
-Kees
--
Kees Cook
next prev parent reply other threads:[~2023-05-31 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 8:33 [PATCH] crypto: marvell/cesa - Fix type mismatch warning Arnd Bergmann
2023-05-23 17:04 ` Kees Cook
2023-05-30 22:48 ` Kees Cook
2023-05-31 10:58 ` Herbert Xu
2023-05-31 16:31 ` Kees Cook [this message]
2023-06-01 10:18 ` Herbert Xu
2023-06-01 14:09 ` Kees Cook
2023-06-02 10:23 ` Herbert Xu
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=202305310930.844EBEA21C@keescook \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=arno@natisbad.org \
--cc=bbrezillon@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schalla@marvell.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