Re: [PATCH] vsock: use sock_error() to consume sk_err after connect timeout

[Stefano Garzarella]

On Mon, Jul 20, 2026 at 05:57:47AM +0800, Nguyen Dinh Phi wrote:
After vsock_connect() exits the wait loop due to sk->sk_err being
set, the error was read but not cleared. This left sk->sk_err set
for subsequent operations.

So, is this a fix? If yes, we should put a Fixes tag.

Also, can you describe how to trigger the issue?

Because I see this in vsock_connect(), so I thought it was in some way 
already handled:

                /* sk_err might have been set as a result of an earlier
                 * (failed) connect attempt.
                 */
                sk->sk_err = 0;

Switch to sock_error() which atomically reads and clears sk->sk_err,
so the error is consumed when returned.

Signed-off-by: Nguyen Dinh Phi <phind....@gmail.com>
Reported-by: syzbot+1b2c9c4a0f8708082...@syzkaller.appspotmail.com

Can you explain how this patch fixes that issue?
(this should be the first information to be put in the commit message 
IMHO)

I'd like to understand better if this is a fix of real bug or just an 
improvement to the code (which is fine by me).

Thanks,
Stefano

---
net/vmw_vsock/af_vsock.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
index 622dbd046799..43eddc33ed12 100644
--- a/net/vmw_vsock/af_vsock.c
+++ b/net/vmw_vsock/af_vsock.c
@@ -1847,14 +1847,11 @@ static int vsock_connect(struct socket *sock, struct 
sockaddr_unsized *addr,
                prepare_to_wait(sk_sleep(sk), &wait, TASK_INTERRUPTIBLE);
        }

-       if (sk->sk_err) {
-               err = -sk->sk_err;
+       err = sock_error(sk);
+       if (err) {
                sk->sk_state = TCP_CLOSE;
                sock->state = SS_UNCONNECTED;
-       } else {
-               err = 0;
        }
-
out_wait:
        finish_wait(sk_sleep(sk), &wait);
out:
--
2.53.0