From: Kun Song <Kun.Song@windriver.com>
To: <gaurav.jain@nxp.com>
Cc: <Kun.Song@windriver.com>, <V.Sethi@nxp.com>,
<aymen.sghaier@nxp.com>, <davem@davemloft.net>,
<filip.pudak@windriver.com>, <heng.guo@windriver.com>,
<herbert@gondor.apana.org.au>, <horia.geanta@nxp.com>,
<linux-crypto@vger.kernel.org>, <meenakshi.aggarwal@nxp.com>,
<richard.danter@windriver.com>
Subject: RE: [PATCH v5.10.y] crypto: caam/jr - Fix possible caam_jr crash
Date: Wed, 10 Jan 2024 16:25:32 +0800 [thread overview]
Message-ID: <20240110082532.2858045-1-Kun.Song@windriver.com> (raw)
In-Reply-To: <AM0PR04MB6004B82755A53A216D2EFA13E7692@AM0PR04MB6004.eurprd04.prod.outlook.com>
>Hello SK
>
>I am submitting and replying patches using gaurav.jain@nxp.com
>
>In Later kernel versions we have provided fixes related to job ring flush and there are other changes as well.
>It would be better to add these changes on top of 5.10 tree as we also run multiple tests and not observed this issue.
>
>Regards
>Gaurav Jain
Hi, Gaurav
Can you identify which commits?
Our version has added some related commits based on 5.10
-------------------------------------------------
04ff8e37a2df crypto: caam/jr - add .shutdown hook
f7ea4a6a6511 LF-3093-1 crypto: caam/jr - fix caam-keygen exit / clean-up
c41daf27fa44 LF-3079 crypto: caam/jr - fix shared IRQ line handling
1f12127de72a MLK-24912-2 crypto: caam - fix RNG vs. hwrng kthread race
04e3a61f9bb5 MLK-24912-1 crypto: caam/jr - update jr_list during suspend/resume
f48d9e23262e MLK-24420-3 crypto: caam - add ioctl calls for black keys and blobs generation
5c98742fbf60 MLK-24420-2 crypto: caam - add support for black keys and blobs
-------------------------------------------------
But We have no way to port this commit because its architecture has changed too much.
commit 304a2efe9d55875c6805f3c2957bc39ceebbc5c0
crypto: caam/jr - Convert to platform remove callback returning void
On your test enviroment, modify function caam_jr_remove
Test scenarios1:
if &jrpriv->tfm_count is not zero,whether will crash?
+atomic_inc(&jrpriv->tfm_count);
if (atomic_read(&jrpriv->tfm_count)) {
Thanks!
BR/SK
next prev parent reply other threads:[~2024-01-10 8:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 9:32 [PATCH v5.10.y] crypto: caam/jr - Fix possible caam_jr crash Kun Song
2023-12-22 11:43 ` Gaurav Jain (OSS)
2023-12-25 3:05 ` Kun Song
2024-01-10 1:39 ` [REMINDER] " Kun Song
2024-01-10 6:57 ` Gaurav Jain (OSS)
2024-01-10 7:00 ` Gaurav Jain
2024-01-10 8:25 ` Kun Song [this message]
2024-01-10 9:14 ` [EXT] " Gaurav Jain
2024-01-10 11:56 ` Kun Song
2024-01-11 10:46 ` [EXT] " Gaurav Jain
2024-01-31 13:34 ` Horia Geanta
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=20240110082532.2858045-1-Kun.Song@windriver.com \
--to=kun.song@windriver.com \
--cc=V.Sethi@nxp.com \
--cc=aymen.sghaier@nxp.com \
--cc=davem@davemloft.net \
--cc=filip.pudak@windriver.com \
--cc=gaurav.jain@nxp.com \
--cc=heng.guo@windriver.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=meenakshi.aggarwal@nxp.com \
--cc=richard.danter@windriver.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