All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH v2 0/2] crypto: mxs_dcp: Fix an Oops on i.MX6ULL
Date: Mon, 19 Jul 2021 22:53:28 +0200 (CEST)	[thread overview]
Message-ID: <979259086.46878.1626728008847.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <2628c3a9-a337-ccee-b996-803fdfe9e1fd@seco.com>

----- 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

WARNING: multiple messages have this Message-ID (diff)
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>
Subject: Re: [PATCH v2 0/2] crypto: mxs_dcp: Fix an Oops on i.MX6ULL
Date: Mon, 19 Jul 2021 22:53:28 +0200 (CEST)	[thread overview]
Message-ID: <979259086.46878.1626728008847.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <2628c3a9-a337-ccee-b996-803fdfe9e1fd@seco.com>

----- 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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-07-19 21:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01 18:56 [PATCH v2 0/2] crypto: mxs_dcp: Fix an Oops on i.MX6ULL Sean Anderson
2021-07-01 18:56 ` Sean Anderson
2021-07-01 18:56 ` [PATCH v2 1/2] crypto: mxs-dcp: Check for DMA mapping errors Sean Anderson
2021-07-01 18:56   ` Sean Anderson
2021-07-01 19:59   ` Richard Weinberger
2021-07-01 19:59     ` Richard Weinberger
2021-07-01 18:56 ` [PATCH v2 2/2] crypto: mxs_dcp: Use sg_mapping_iter to copy data Sean Anderson
2021-07-01 18:56   ` Sean Anderson
2021-07-01 19:59   ` Richard Weinberger
2021-07-01 19:59     ` Richard Weinberger
2021-07-01 20:04     ` Sean Anderson
2021-07-01 20:04       ` Sean Anderson
2021-07-01 19:28 ` [PATCH v2 0/2] crypto: mxs_dcp: Fix an Oops on i.MX6ULL Richard Weinberger
2021-07-01 19:28   ` Richard Weinberger
2021-07-01 20:03   ` Sean Anderson
2021-07-01 20:30   ` Sean Anderson
2021-07-01 20:30     ` Sean Anderson
2021-07-15 15:10     ` Sean Anderson
2021-07-15 15:10       ` Sean Anderson
2021-07-19 20:53       ` Richard Weinberger [this message]
2021-07-19 20:53         ` Richard Weinberger
2021-07-16  8:14 ` Herbert Xu
2021-07-16  8:14   ` Herbert Xu

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=979259086.46878.1626728008847.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=aymen.sghaier@nxp.com \
    --cc=davem@davemloft.net \
    --cc=david@sigma-star.at \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=sean.anderson@seco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.