Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 19 Jul 2021 22:53:28 +0200 (CEST)
From:   Richard Weinberger <richard@nod.at>
To:     Sean Anderson <sean.anderson@seco.com>
Cc:     Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
        Herbert Xu <herbert@gondor.apana.org.au>,
        davem <davem@davemloft.net>, horia geanta <horia.geanta@nxp.com>,
        aymen sghaier <aymen.sghaier@nxp.com>,
        linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
        Marek Vasut <marex@denx.de>, david <david@sigma-star.at>
Message-ID: <979259086.46878.1626728008847.JavaMail.zimbra@nod.at>
In-Reply-To: <2628c3a9-a337-ccee-b996-803fdfe9e1fd@seco.com>
References: <20210701185638.3437487-1-sean.anderson@seco.com> <723802567.13207.1625167719840.JavaMail.zimbra@nod.at> <dbeafb2a-e631-ad51-05b3-a775225140d6@seco.com> <2628c3a9-a337-ccee-b996-803fdfe9e1fd@seco.com>
Subject: Re: [PATCH v2 0/2] crypto: mxs_dcp: Fix an Oops on i.MX6ULL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8BIT
Thread-Topic: crypto: mxs_dcp: Fix an Oops on i.MX6ULL
Thread-Index: Hx63mEBJVVrE3nFBLOnyq/wnxKO8fg==
Precedence: bulk

----- Ursprüngliche Mail -----
>>>> but got the same oops. Unfortunately, I don't have the time to
>>>> investigate this oops as well. I'd appreciate if anyone else using this
>>>> device could look into this and see if they encounter the same errors.
>>>>
>>>> [1] https://github.com/smuellerDD/libkcapi/blob/master/test/kcapi-dgst-test.sh
>>>
>>>  Can you please share your kernel .config? David or I can test on our test bed.
>>>  But will take a few days.
> 
> Were you able to reproduce these oopses?

Thanks for the reminder!
No, I was not able to reproduce.
Just tested again with Herbert's cryptodev-2.6.git repo.
I'll run the tests a few more times, maybe it just needs more time...

Thanks,
//richard