[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250108110457.1514-1-hdanton@sina.com>
Date: Wed, 8 Jan 2025 19:04:56 +0800
From: Hillf Danton <hdanton@...a.com>
To: syzbot <syzbot+6ac73b3abf1b598863fa@...kaller.appspotmail.com>
Cc: Sabrina Dubroca <sd@...asysnail.net>,
borisp@...dia.com,
edumazet@...gle.com,
linux-kernel@...r.kernel.org,
netdev@...r.kernel.org,
pabeni@...hat.com,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [net?] INFO: task hung in lock_sock_nested (5)
On 2024-12-26, 01:34:19 -0800, syzbot wrote:
> syzbot found the following issue on:
>
> HEAD commit: 9268abe611b0 Merge branch 'net-lan969x-add-rgmii-support'
> git tree: net-next
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=155c0018580000
Test Sabrina's patch.
#syz test
--- x/net/tls/tls_main.c
+++ y/net/tls/tls_main.c
@@ -737,6 +737,8 @@ static int do_tls_setsockopt_conf(struct
else
ctx->rx_conf = conf;
update_sk_prot(sk, ctx);
+ if (update)
+ return 0;
if (tx) {
ctx->sk_write_space = sk->sk_write_space;
sk->sk_write_space = tls_write_space;
--
Powered by blists - more mailing lists