From: John Fastabend <john.fastabend@gmail.com>
To: Andre Tomt <andre@tomt.net>,
John Fastabend <john.fastabend@gmail.com>,
"Steinar H. Gunderson" <steinar+kernel@gunderson.no>,
netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: kTLS broken somewhere between 4.18 and 5.0
Date: Tue, 07 May 2019 07:45:26 -0700 [thread overview]
Message-ID: <5cd19a06c0ec1_7e362b112aa185b8da@john-XPS-13-9360.notmuch> (raw)
In-Reply-To: <a69bb5f9-45d2-354e-0422-e3d37d4e427d@tomt.net>
Andre Tomt wrote:
> On 14.04.2019 22:40, John Fastabend wrote:
> > On 4/13/19 6:56 PM, Andre Tomt wrote:
> >> On 13.04.2019 17:34, Steinar H. Gunderson wrote:
> >>> Hi,
> >>>
> >>> I've been using kTLS for a while, with my video reflector Cubemap
> >>> (https://git.sesse.net/?p=cubemap). After I upgraded my server from
> >>> 4.18.11 to 5.0.6, seemingly I've started seeing corruption. The data sent
> >>> with send() (HTTP headers, HLS playlists) appears to be fine, but sendfile()
> >>> (actual video data, from a file on tmpfs) is not; after ~20 kB of data
> >>> (19626 in one test here), the data appears to be randomly corrupted. Diffing
> >>> non-TLS (good) and TLS (bad) video data:
[...]
> Hi John
>
> Have you had any luck tracking this down?
>
> Just gave net.git a spin and it is still serving up corrupted data when
> ktls is active and using sendfile. FWIW I only tested without ktls
> offload capable hardware (ie in software mode) and no bpf. Same sendfile
> usage on a non-ktls socket works fine.
Hi Andre, I should have a series to address this in the next few days. I
still need to resolve a couple corner cases. Hopefully, by next week we
can get bpf tree working for this case.
Thanks,
John
next prev parent reply other threads:[~2019-05-07 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 15:34 kTLS broken somewhere between 4.18 and 5.0 Steinar H. Gunderson
2019-04-14 1:56 ` Andre Tomt
2019-04-14 20:40 ` John Fastabend
2019-05-02 14:15 ` Andre Tomt
2019-05-07 14:45 ` John Fastabend [this message]
2019-05-30 22:41 ` Andre Tomt
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=5cd19a06c0ec1_7e362b112aa185b8da@john-XPS-13-9360.notmuch \
--to=john.fastabend@gmail.com \
--cc=andre@tomt.net \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=steinar+kernel@gunderson.no \
/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