From: "neil.armstrong@linaro.org" <neil.armstrong@linaro.org>
To: Alexey Romanov <avromanov@salutedevices.com>,
Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: "clabbe@baylibre.com" <clabbe@baylibre.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"khilman@baylibre.com" <khilman@baylibre.com>,
"jbrunet@baylibre.com" <jbrunet@baylibre.com>,
"martin.blumenstingl@googlemail.com"
<martin.blumenstingl@googlemail.com>,
"vadim.fedorenko@linux.dev" <vadim.fedorenko@linux.dev>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-amlogic@lists.infradead.org"
<linux-amlogic@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
kernel <kernel@sberdevices.ru>
Subject: Re: [PATCH v4 00/20] Support more Amlogic SoC families in crypto driver
Date: Thu, 29 Feb 2024 16:14:10 +0100 [thread overview]
Message-ID: <456a6aa7-60e0-4a56-9efa-731f717012ac@linaro.org> (raw)
In-Reply-To: <20240229025337.ftbvoaafmu5zvyha@cab-wsm-0029881>
On 29/02/2024 14:05, Alexey Romanov wrote:
> Hello!
>
> On Wed, Feb 28, 2024 at 09:19:32PM +0100, Corentin Labbe wrote:
>> Le Wed, Feb 28, 2024 at 01:37:02PM +0000, Alexey Romanov a 'ecrit :
>>> Hello,
>>>
>>> On Mon, Feb 19, 2024 at 07:57:27AM +0100, Corentin Labbe wrote:
>>>> Le Thu, Feb 15, 2024 at 10:47:24AM +0000, Alexey Romanov a 'ecrit :
>>>>> On Tue, Feb 13, 2024 at 08:21:12AM +0100, Corentin Labbe wrote:
>>>>>> Le Mon, Feb 12, 2024 at 04:50:48PM +0300, Alexey Romanov a 'ecrit :
>>>>>>> Hello!
>>>>>>>
>>>>>>> This patchset expand the funcionality of the Amlogic
>>>>>>> crypto driver by adding support for more SoC families:
>>>>>>> AXG, G12A, G12B, SM1, A1, S4.
>>>>>>>
>>>>>>> Also specify and enable crypto node in device tree
>>>>>>> for reference Amlogic devices.
>>>>>>>
>>>>>>> Tested on AXG, G12A/B, SM1, A1 and S4 devices via
>>>>>>> custom tests [1] and tcrypt module.
>>>>>>>
>>>>>>> ---
>>>>>>>
>>>>>>
>>>>>> added patchs up to "drivers: crypto: meson: process more than MAXDESCS descriptors"
>>>>>
>>>>> Including this patch or not?
>>>>
>>>> The crash start with "drivers: crypto: meson: move algs definition and cipher API to cipher.c"
>>>
>>> Unfortunately I was unable to reproduce this. I use Khadas Vim1 board
>>> and my custom tests (https://gist.github.com/mRrvz/3fb8943a7487ab7b943ec140706995e7).
>>> Tried both build as module and built-in.
>>>
>>> Can you, please, give more information? Maybe your test cases?
>>
>> My test case is simple, simply load the driver.
>>
>> The problem is that you moved the algs[i].mc = mc after the register of algs (in drivers: crypto: meson: move algs definition and cipher API to cipher.c)
>> Test could happen as soon the register is done and so mc is deferenced.
>
> Yeah, you are right. Will fix it. Thank you.
>
>>
>> Since you didnt hit the case, I suspect you didnt test the driver as module.
>
> No, I test the driver as module.
> I think the problem is that on my system no one uses this crypto backend
> outside of my tests module, unlike your system.
I reproduced the issue, testing each commit with enabled runtime cryto tests:
I get the following when applying "drivers: crypto: meson: introduce hasher":
[ 4.514031] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[ 4.517193] Mem abort info:
[ 4.519934] ESR = 0x0000000086000004
[ 4.523641] EC = 0x21: IABT (current EL), IL = 32 bits
[ 4.528903] SET = 0, FnV = 0
[ 4.531920] EA = 0, S1PTW = 0
[ 4.535025] FSC = 0x04: level 0 translation fault
[ 4.539856] [0000000000000000] user address but active_mm is swapper
[ 4.546155] Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP
[ 4.552359] Modules linked in:
[ 4.555376] CPU: 2 PID: 77 Comm: cryptomgr_test Not tainted 6.8.0-rc6-next-20240229-g2296d426c21a #105
[ 4.564608] Hardware name: Libre Computer AML-S905X-CC (DT)
[ 4.570125] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 4.577025] pc : 0x0
[ 4.579178] lr : ahash_def_finup+0x12c/0x14c
[ 4.583406] sp : ffff8000825037a0
[ 4.586683] x29: ffff8000825037a0 x28: 0000000000000001 x27: ffff000007ab8060
[ 4.593758] x26: ffff800082503958 x25: 0000000000000400 x24: ffff800082503918
[ 4.600830] x23: 0000000000000820 x22: ffff0000048ec390 x21: ffff000003d9e200
[ 4.607903] x20: ffff0000048ee300 x19: ffff000003d9e400 x18: 0000000000000020
[ 4.614976] x17: 00000000b5f74d5b x16: ffff800081bbbc60 x15: ffffffffffffffff
[ 4.622048] x14: ffff0000049fb380 x13: 0000000000000000 x12: 0000000000000000
[ 4.629120] x11: ffff800082503778 x10: ffff800082503780 x9 : 0000000000001388
[ 4.636193] x8 : ffff800082503988 x7 : fefefefefefefefe x6 : 0101010101010101
[ 4.643265] x5 : ffff0000049fb300 x4 : ffff00007f2d5830 x3 : 0000000000000000
[ 4.650338] x2 : 0000000000000000 x1 : ffff0000048ee300 x0 : ffff000003d9e200
[ 4.657411] Call trace:
[ 4.659823] 0x0
[ 4.661633] crypto_ahash_finup+0x38/0x44
[ 4.665602] test_ahash_vec_cfg+0x680/0x7dc
[ 4.669742] test_hash_vec+0xac/0x1ec
[ 4.673364] __alg_test_hash+0x158/0x308
[ 4.677246] alg_test_hash+0xfc/0x1a0
[ 4.680868] alg_test.part.0+0x51c/0x524
[ 4.684750] alg_test+0x20/0x64
[ 4.687854] cryptomgr_test+0x24/0x44
[ 4.691477] kthread+0x118/0x11c
[ 4.694668] ret_from_fork+0x10/0x20
[ 4.698214] Code: ???????? ???????? ???????? ???????? (????????)
[ 4.704247] ---[ end trace 0000000000000000 ]---
Please make sure every single commit builds without error and doesn't regress at runtime on existing platforms.
Thanks,
Neil
>
>>
>> Regards
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2024-02-29 15:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 13:50 [PATCH v4 00/20] Support more Amlogic SoC families in crypto driver Alexey Romanov
2024-02-12 13:50 ` [PATCH v4 01/20] drivers: crypto: meson: don't hardcode IRQ count Alexey Romanov
2024-02-12 13:50 ` [PATCH v4 02/20] drviers: crypto: meson: add platform data Alexey Romanov
2024-02-12 17:08 ` neil.armstrong
2024-02-12 13:50 ` [PATCH v4 03/20] drivers: crypto: meson: make CLK controller optional Alexey Romanov
2024-02-12 17:10 ` neil.armstrong
2024-02-12 13:50 ` [PATCH v4 04/20] drivers: crypto: meson: add MMIO helpers Alexey Romanov
2024-02-12 17:11 ` neil.armstrong
2024-02-12 13:50 ` [PATCH v4 05/20] drivers: crypto: meson: move get_engine_number() Alexey Romanov
2024-02-12 17:11 ` neil.armstrong
2024-02-12 13:50 ` [PATCH v4 06/20] drivers: crypto: meson: drop status field from meson_flow Alexey Romanov
2024-02-12 17:12 ` neil.armstrong
2024-02-12 13:50 ` [PATCH v4 07/20] drivers: crypto: meson: move algs definition and cipher API to cipher.c Alexey Romanov
2024-02-12 17:12 ` neil.armstrong
2024-02-12 13:50 ` [PATCH v4 08/20] drivers: crypto: meson: cleanup defines Alexey Romanov
2024-02-12 17:14 ` neil.armstrong
2024-02-12 13:50 ` [PATCH v4 09/20] drivers: crypto: meson: process more than MAXDESCS descriptors Alexey Romanov
2024-02-12 13:50 ` [PATCH v4 10/20] drivers: crypto: meson: avoid kzalloc in engine thread Alexey Romanov
2024-02-12 17:15 ` neil.armstrong
2024-02-12 13:50 ` [PATCH v4 11/20] drivers: crypto: meson: introduce hasher Alexey Romanov
2024-02-12 13:51 ` [PATCH v4 12/20] drivers: crypto: meson: add support for AES-CTR Alexey Romanov
2024-02-12 13:51 ` [PATCH v4 13/20] drivers: crypto: meson: use fallback for 192-bit keys Alexey Romanov
2024-02-12 13:51 ` [PATCH v4 14/20] drivers: crypto: meson: add support for G12-series Alexey Romanov
2024-02-12 13:51 ` [PATCH v4 15/20] drivers: crypto: meson: add support for AXG-series Alexey Romanov
2024-02-12 13:51 ` [PATCH v4 16/20] dt-bindings: crypto: meson: support new SoC's Alexey Romanov
2024-02-15 14:28 ` Rob Herring
2024-02-12 13:51 ` [PATCH v4 17/20] arch: arm64: dts: meson: a1: add crypto node Alexey Romanov
2024-02-12 17:04 ` neil.armstrong
2024-02-12 13:51 ` [PATCH v4 18/20] arch: arm64: dts: meson: s4: " Alexey Romanov
2024-02-12 17:04 ` neil.armstrong
2024-02-12 13:51 ` [PATCH v4 19/20] arch: arm64: dts: meson: g12: " Alexey Romanov
2024-02-12 17:04 ` neil.armstrong
2024-02-12 13:51 ` [PATCH v4 20/20] arch: arm64: dts: meson: axg: " Alexey Romanov
2024-02-12 17:04 ` neil.armstrong
2024-02-12 17:04 ` [PATCH v4 00/20] Support more Amlogic SoC families in crypto driver neil.armstrong
2024-02-13 7:21 ` Corentin Labbe
2024-02-15 10:43 ` Alexey Romanov
2024-02-15 10:47 ` Alexey Romanov
2024-02-19 6:57 ` Corentin Labbe
2024-02-28 13:37 ` Alexey Romanov
2024-02-28 20:19 ` Corentin Labbe
2024-02-29 13:05 ` Alexey Romanov
2024-02-29 15:14 ` neil.armstrong [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=456a6aa7-60e0-4a56-9efa-731f717012ac@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=avromanov@salutedevices.com \
--cc=clabbe.montjoie@gmail.com \
--cc=clabbe@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jbrunet@baylibre.com \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=robh+dt@kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).