[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220119092440.4045-1-miles.chen@mediatek.com>
Date: Wed, 19 Jan 2022 17:24:40 +0800
From: Miles Chen <miles.chen@...iatek.com>
To: <jason@...c4.com>
CC: <ardb@...nel.org>, <davem@...emloft.net>,
<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>
Subject: Re: [PATCH] lib/crypto: blake2s: fix a CFI failure
hi,
>Thanks for the patch. Could you let me know which architecture and
>compiler this was broken on? If I had to guess, I'd wager arm32, and
>you hit this by enabling optimized blake2s?
Actually, I am merging android-common tree and test our device.
I use arm64 and clang-r437112b.
I'm not sure which option is the right one, grep 'BLAKE' .config shows:
CONFIG_CRYPTO_BLAKE2B=y
# CONFIG_CRYPTO_BLAKE2S is not set
# CONFIG_CRYPTO_LIB_BLAKE2S_GENERIC=y
and... I found that my patch breaks arm32 build, sorry for that.
>If so, I'm not sure the problem is with weak symbols. Why should CFI
>break weak symbols? Rather, perhaps the issue is that the function is
>defined in blake2s-core.S? Are there some CFI macros we need for that
>definition?
Powered by blists - more mailing lists