linux-kernel - Re: [PATCH] VSOCK: Don't set sk_state to TCP

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20171128.160204.772077471252633195.davem@davemloft.net>
Date:   Tue, 28 Nov 2017 16:02:04 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     jhansen@...are.com
Cc:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        virtualization@...ts.linux-foundation.org,
        gregkh@...uxfoundation.org, pv-drivers@...are.com,
        stefanha@...hat.com
Subject: Re: [PATCH] VSOCK: Don't set sk_state to TCP_CLOSE before testing
 it

From: Jorgen Hansen <jhansen@...are.com>
Date: Mon, 27 Nov 2017 05:29:32 -0800

> A recent commit (3b4477d2dcf2) converted the sk_state to use
> TCP constants. In that change, vmci_transport_handle_detach
> was changed such that sk->sk_state was set to TCP_CLOSE before
> we test whether it is TCP_SYN_SENT. This change moves the
> sk_state change back to the original locations in that function.
> 
> Signed-off-by: Jorgen Hansen <jhansen@...are.com>

Applied.