From: Jakub Kicinski <kuba@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "Steffen Trumtrar" <s.trumtrar@pengutronix.de>,
linux-crypto@vger.kernel.org, io-uring@vger.kernel.org,
kernel@pengutronix.de, "Horia Geantă" <horia.geanta@nxp.com>,
"Pankaj Gupta" <pankaj.gupta@nxp.com>,
"Gaurav Jain" <gaurav.jain@nxp.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Pavel Begunkov" <asml.silence@gmail.com>,
"Boris Pismenny" <borisp@nvidia.com>,
"John Fastabend" <john.fastabend@gmail.com>,
"Daniel Borkmann" <daniel@iogearbox.net>,
netdev@vger.kernel.org
Subject: Re: [BUG] Layerscape CAAM+kTLS+io_uring
Date: Thu, 5 May 2022 17:10:00 -0700 [thread overview]
Message-ID: <20220505171000.48a9155b@kernel.org> (raw)
In-Reply-To: <20220505192046.hczmzg7k6tz2rjv3@pengutronix.de>
On Thu, 5 May 2022 21:20:46 +0200 Marc Kleine-Budde wrote:
> Hello,
>
> no one seems to care about this problem. :/
>
> Maybe too many components are involved, I'm the respective maintainers
> on Cc.
>
> Cc += the CAAM maintainers
> Cc += the io_uring maintainers
> Cc += the kTLS maintainers
>
> On 27.04.2022 10:20:40, Steffen Trumtrar wrote:
> > Hi all,
> >
> > I have a Layerscape-1046a based board where I'm trying to use a
> > combination of liburing (v2.0) with splice, kTLS and CAAM (kernel
> > v5.17). The problem I see is that on shutdown the last bytes are
> > missing. It looks like io_uring is not waiting for all completions
> > from the CAAM driver.
> >
> > With ARM-ASM instead of the CAAM, the setup works fine.
>
> What's the difference between the CAAM and ARM-ASM crypto? Without
> looking into the code I think the CAAM is asynchron while ARM-ASM is
> synchron. Is this worth investigating?
Sounds like
20ffc7adf53a ("net/tls: missing received data after fast remote close")
next prev parent reply other threads:[~2022-05-06 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 8:20 [BUG] Layerscape CAAM+kTLS+io_uring Steffen Trumtrar
2022-05-05 19:20 ` Marc Kleine-Budde
2022-05-06 0:10 ` Jakub Kicinski [this message]
2022-05-16 10:06 ` Steffen Trumtrar
2022-05-17 6:30 ` [EXT] " Gaurav Jain
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=20220505171000.48a9155b@kernel.org \
--to=kuba@kernel.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=borisp@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=gaurav.jain@nxp.com \
--cc=horia.geanta@nxp.com \
--cc=io-uring@vger.kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-crypto@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=s.trumtrar@pengutronix.de \
/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.