[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220119094342.4515-1-miles.chen@mediatek.com>
Date: Wed, 19 Jan 2022 17:43:42 +0800
From: Miles Chen <miles.chen@...iatek.com>
To: <ardb@...nel.org>
CC: <Jason@...c4.com>, <davem@...emloft.net>, <ebiggers@...gle.com>,
<gregkh@...uxfoundation.org>, <herbert@...dor.apana.org.au>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-crypto@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-mediatek@...ts.infradead.org>, <matthias.bgg@...il.com>,
<miles.chen@...iatek.com>, <samitolvanen@...gle.com>
Subject: Re: [PATCH] lib/crypto: blake2s: fix a CFI failure
>Ehm, maybe not. As Jason points out, the typedef does not have quite
>the right type, so that is most likely the culprit, and this
>workaround would trigger CFI in exactly the same way.
>
>Interestingly, the compiler does not seem to mind, right? Or are you
>seeing any build time warnings on the reference to blake2s_compress in
>the call to __blake2s_update() ?
No, no warnings as the -Wcast-function-type is globally enabled.
I cleaned some cast-function-type errors but no warnings in
__blake2s_update.
Miles
Powered by blists - more mailing lists