netdev - Re: [PATCH v2] vsock: remove vsock from connected table when connect is interrupted by a signal

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>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <164511841010.26117.4554387084228726127.git-patchwork-notify@kernel.org>
Date:   Thu, 17 Feb 2022 17:20:10 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Seth Forshee <sforshee@...italocean.com>
Cc:     sgarzare@...hat.com, davem@...emloft.net, kuba@...nel.org,
        virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] vsock: remove vsock from connected table when connect is
 interrupted by a signal

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@...nel.org>:

On Thu, 17 Feb 2022 08:13:12 -0600 you wrote:
> vsock_connect() expects that the socket could already be in the
> TCP_ESTABLISHED state when the connecting task wakes up with a signal
> pending. If this happens the socket will be in the connected table, and
> it is not removed when the socket state is reset. In this situation it's
> common for the process to retry connect(), and if the connection is
> successful the socket will be added to the connected table a second
> time, corrupting the list.
> 
> [...]

Here is the summary with links:
  - [v2] vsock: remove vsock from connected table when connect is interrupted by a signal
    https://git.kernel.org/netdev/net/c/b9208492fcae

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html