netdev - Re: [PATCH] tls splice: check SPLICE_F_NONBLOCK instead of MSG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20210517090157.3e37461e@kicinski-fedora-PC1C0HJN>
Date:   Mon, 17 May 2021 09:01:57 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Jim Ma <majinjing3@...il.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] tls splice: check SPLICE_F_NONBLOCK instead of
 MSG_DONTWAIT

On Sun, 16 May 2021 04:58:11 +0000 Jim Ma wrote:
> No, this patch fix using MSG_* in splice.
> 
> I have tested read, write, sendmsg, recvmsg fot tls, and try to
> implement tls in golang. In develop, I have found those issues and
> try to fix them.

To be clear the Fixes tag points to the commit where the issue was
first introduced. AFAICT the issue was there from the start, that
is commit c46234ebb4d1 ("tls: RX path for ktls"). Are you saying that 
it used to work in the beginning and then another commit broke it?

We need the fixes tag to be able to tell how far back (in terms of
LTS releases) to backport.

> An other issue, when before enable TLS_RX in cleint, the server sends
> a tls record, client will receive bad message or message too long
> error. I'm try to fix this issue.

Please reply all and don't top post.