From: "Ihor Solodrai" <ihor.solodrai@linux.dev>
To: "Jakub Kicinski" <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, borisp@nvidia.com,
john.fastabend@gmail.com, sd@queasysnail.net,
"Jakub Kicinski" <kuba@kernel.org>,
syzbot+b4cd76826045a1eb93c1@syzkaller.appspotmail.com,
bpf@vger.kernel.org, jiayuan.chen@linux.dev,
"Alexei Starovoitov" <ast@kernel.org>
Subject: Re: [PATCH net 1/2] net: tls: explicitly disallow disconnect
Date: Tue, 15 Apr 2025 03:16:25 +0000 [thread overview]
Message-ID: <e0ea9f710fde34bdce42515f8c68722015403ab9@linux.dev> (raw)
In-Reply-To: <20250404180334.3224206-1-kuba@kernel.org>
On 4/4/25 11:03 AM, Jakub Kicinski wrote:
> syzbot discovered that it can disconnect a TLS socket and then
> run into all sort of unexpected corner cases. I have a vague
> recollection of Eric pointing this out to us a long time ago.
> Supporting disconnect is really hard, for one thing if offload
> is enabled we'd need to wait for all packets to be _acked_.
> Disconnect is not commonly used, disallow it.
>
> The immediate problem syzbot run into is the warning in the strp,
> but that's just the easiest bug to trigger:
>
> WARNING: CPU: 0 PID: 5834 at net/tls/tls_strp.c:486 tls_strp_msg_load+0x72e/0xa80 net/tls/tls_strp.c:486
> RIP: 0010:tls_strp_msg_load+0x72e/0xa80 net/tls/tls_strp.c:486
> Call Trace:
> <TASK>
> tls_rx_rec_wait+0x280/0xa60 net/tls/tls_sw.c:1363
> tls_sw_recvmsg+0x85c/0x1c30 net/tls/tls_sw.c:2043
> inet6_recvmsg+0x2c9/0x730 net/ipv6/af_inet6.c:678
> sock_recvmsg_nosec net/socket.c:1023 [inline]
> sock_recvmsg+0x109/0x280 net/socket.c:1045
> __sys_recvfrom+0x202/0x380 net/socket.c:2237
>
> Fixes: 3c4d7559159b ("tls: kernel TLS support")
> Reported-by: syzbot+b4cd76826045a1eb93c1@syzkaller.appspotmail.com
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Hi everyone.
This patch has broken a BPF selftest and as a result BPF CI:
* https://github.com/kernel-patches/bpf/actions/runs/14458537639
* https://github.com/kernel-patches/bpf/actions/runs/14457178732
The test in question is test_sockmap_ktls_disconnect_after_delete
(tools/testing/selftests/bpf/prog_tests/sockmap_ktls.c) [1].
Since the test is about disconnect use-case, and the patch disallows
it, I assume it's appropriate to simply remove the test?
Please let me know. Thanks.
[1] https://web.git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/tree/tools/testing/selftests/bpf/prog_tests/sockmap_ktls.c#n28
> ---
> net/tls/tls_main.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/net/tls/tls_main.c b/net/tls/tls_main.c
> index cb86b0bf9a53..a3ccb3135e51 100644
> --- a/net/tls/tls_main.c
> +++ b/net/tls/tls_main.c
> @@ -852,6 +852,11 @@ static int tls_setsockopt(struct sock *sk, int level, int optname,
> return do_tls_setsockopt(sk, optname, optval, optlen);
> }
>
> +static int tls_disconnect(struct sock *sk, int flags)
> +{
> + return -EOPNOTSUPP;
> +}
> +
> struct tls_context *tls_ctx_create(struct sock *sk)
> {
> struct inet_connection_sock *icsk = inet_csk(sk);
> @@ -947,6 +952,7 @@ static void build_protos(struct proto prot[TLS_NUM_CONFIG][TLS_NUM_CONFIG],
> prot[TLS_BASE][TLS_BASE] = *base;
> prot[TLS_BASE][TLS_BASE].setsockopt = tls_setsockopt;
> prot[TLS_BASE][TLS_BASE].getsockopt = tls_getsockopt;
> + prot[TLS_BASE][TLS_BASE].disconnect = tls_disconnect;
> prot[TLS_BASE][TLS_BASE].close = tls_sk_proto_close;
>
> prot[TLS_SW][TLS_BASE] = prot[TLS_BASE][TLS_BASE];
next prev parent reply other threads:[~2025-04-15 3:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 18:03 [PATCH net 1/2] net: tls: explicitly disallow disconnect Jakub Kicinski
2025-04-04 18:03 ` [PATCH net 2/2] selftests: tls: check that disconnect does nothing Jakub Kicinski
2025-04-07 13:07 ` Sabrina Dubroca
2025-04-04 18:12 ` [PATCH net 1/2] net: tls: explicitly disallow disconnect Eric Dumazet
2025-04-07 13:02 ` Sabrina Dubroca
2025-04-08 9:50 ` patchwork-bot+netdevbpf
2025-04-15 3:16 ` Ihor Solodrai [this message]
2025-04-15 8:24 ` Paolo Abeni
2025-04-15 10:43 ` Jiayuan Chen
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=e0ea9f710fde34bdce42515f8c68722015403ab9@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=borisp@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=syzbot+b4cd76826045a1eb93c1@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).