From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <tkhai@ya.ru>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<kuniyu@amazon.com>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>
Subject: Re: [PATCH net v2] unix: Fix race in SOCK_SEQPACKET's unix_dgram_sendmsg()
Date: Sun, 27 Nov 2022 08:35:59 +0900 [thread overview]
Message-ID: <20221126233559.31979-1-kuniyu@amazon.com> (raw)
In-Reply-To: <bd4d533b-15d2-6c0a-7667-70fd95dbea20@ya.ru>
From: Kirill Tkhai <tkhai@ya.ru>
Date: Sun, 27 Nov 2022 01:46:51 +0300
> There is a race resulting in alive SOCK_SEQPACKET socket
> may change its state from TCP_ESTABLISHED to TCP_CLOSE:
>
> unix_release_sock(peer) unix_dgram_sendmsg(sk)
> sock_orphan(peer)
> sock_set_flag(peer, SOCK_DEAD)
> sock_alloc_send_pskb()
> if !(sk->sk_shutdown & SEND_SHUTDOWN)
> OK
> if sock_flag(peer, SOCK_DEAD)
> sk->sk_state = TCP_CLOSE
> sk->sk_shutdown = SHUTDOWN_MASK
>
>
> After that socket sk remains almost normal: it is able to connect, listen, accept
> and recvmsg, while it can't sendmsg.
>
> Since this is the only possibility for alive SOCK_SEQPACKET to change
> the state in such way, we should better fix this strange and potentially
> danger corner case.
>
> Also, move TCP_CLOSE assignment for SOCK_DGRAM sockets under state lock
> to fix race with unix_dgram_connect():
>
> unix_dgram_connect(other) unix_dgram_sendmsg(sk)
> unix_peer(sk) = NULL
> unix_state_unlock(sk)
> unix_state_double_lock(sk, other)
> sk->sk_state = TCP_ESTABLISHED
> unix_peer(sk) = other
> unix_state_double_unlock(sk, other)
> sk->sk_state = TCP_CLOSED
>
> This patch fixes both of these races.
>
> Fixes: 83301b5367a9 ("af_unix: Set TCP_ESTABLISHED for datagram sockets too")
> Suggested-by: Kuniyuki Iwashima <kuniyu@amazon.com>
> Signed-off-by: Kirill Tkhai <tkhai@ya.ru>
Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
Thank you, Kirill.
> ---
> v2: Disconnect from peer right there.
>
> net/unix/af_unix.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
> index b3545fc68097..be40023a61fb 100644
> --- a/net/unix/af_unix.c
> +++ b/net/unix/af_unix.c
> @@ -2001,11 +2001,14 @@ static int unix_dgram_sendmsg(struct socket *sock, struct msghdr *msg,
> err = 0;
> if (unix_peer(sk) == other) {
> unix_peer(sk) = NULL;
> - unix_dgram_peer_wake_disconnect_wakeup(sk, other);
> +
> + if (sk->sk_type == SOCK_DGRAM) {
> + unix_dgram_peer_wake_disconnect_wakeup(sk, other);
> + sk->sk_state = TCP_CLOSE;
> + }
>
> unix_state_unlock(sk);
>
> - sk->sk_state = TCP_CLOSE;
> unix_dgram_disconnected(sk, other);
> sock_put(other);
> err = -ECONNREFUSED;
next prev parent reply other threads:[~2022-11-26 23:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 22:46 [PATCH net v2] unix: Fix race in SOCK_SEQPACKET's unix_dgram_sendmsg() Kirill Tkhai
2022-11-26 23:35 ` Kuniyuki Iwashima [this message]
2022-12-01 9:30 ` Paolo Abeni
2022-12-02 22:43 ` Kirill Tkhai
2022-12-02 23:18 ` Iwashima, Kuniyuki
2022-12-05 9:22 ` Paolo Abeni
2022-12-05 17:07 ` Kirill Tkhai
2022-12-03 10:37 ` Kirill Tkhai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221126233559.31979-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tkhai@ya.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).