netdev - Re: [PATCH net-next] unix: Guarantee sk_state relevance in case of it was assigned by a task on other cpu

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

Message-ID: <20230124173557.2b13e194@kernel.org>
Date:   Tue, 24 Jan 2023 17:35:57 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Kirill Tkhai <tkhai@...ru>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>,
        davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
        kuniyu@...zon.com, gorcunov@...il.com
Subject: Re: [PATCH net-next] unix: Guarantee sk_state relevance in case of
 it was assigned by a task on other cpu

On Mon, 23 Jan 2023 01:21:20 +0300 Kirill Tkhai wrote:
> Since in this situation unix_accept() is called chronologically later, such
> behavior is not obvious and it is wrong.

Noob question, perhaps - how do we establish the ordering ?
CPU1 knows that listen() has succeed without a barrier ?