From: Michal Luczaj <mhal@rbox.co>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH net-next v3 3/4] vsock: Move lingering logic to af_vsock core
Date: Wed, 30 Apr 2025 13:11:48 +0200 [thread overview]
Message-ID: <f1943412-ccbf-4913-a5c5-818f0f586db1@rbox.co> (raw)
In-Reply-To: <CAGxU2F62CTUKVjuG9Fjo29E6uopVzOK8zgr+HwooqMr4V_RvLQ@mail.gmail.com>
On 4/30/25 12:37, Stefano Garzarella wrote:
> On Wed, 30 Apr 2025 at 12:33, Michal Luczaj <mhal@rbox.co> wrote:
>>
>> On 4/30/25 11:36, Stefano Garzarella wrote:
>>> On Wed, Apr 30, 2025 at 11:10:29AM +0200, Michal Luczaj wrote:
>>>> Lingering should be transport-independent in the long run. In preparation
>>>> for supporting other transports, as well the linger on shutdown(), move
>>>> code to core.
>>>>
>>>> Guard against an unimplemented vsock_transport::unsent_bytes() callback.
>>>>
>>>> Suggested-by: Stefano Garzarella <sgarzare@redhat.com>
>>>> Signed-off-by: Michal Luczaj <mhal@rbox.co>
>>>> ---
>>>> include/net/af_vsock.h | 1 +
>>>> net/vmw_vsock/af_vsock.c | 25 +++++++++++++++++++++++++
>>>> net/vmw_vsock/virtio_transport_common.c | 23 +----------------------
>>>> 3 files changed, 27 insertions(+), 22 deletions(-)
>>>>
>>>> diff --git a/include/net/af_vsock.h b/include/net/af_vsock.h
>>>> index 9e85424c834353d016a527070dd62e15ff3bfce1..bd8b88d70423051dd05fc445fe37971af631ba03 100644
>>>> --- a/include/net/af_vsock.h
>>>> +++ b/include/net/af_vsock.h
>>>> @@ -221,6 +221,7 @@ void vsock_for_each_connected_socket(struct vsock_transport *transport,
>>>> void (*fn)(struct sock *sk));
>>>> int vsock_assign_transport(struct vsock_sock *vsk, struct vsock_sock *psk);
>>>> bool vsock_find_cid(unsigned int cid);
>>>> +void vsock_linger(struct sock *sk, long timeout);
>>>>
>>>> /**** TAP ****/
>>>>
>>>> diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
>>>> index fc6afbc8d6806a4d98c66abc3af4bd139c583b08..946b37de679a0e68b84cd982a3af2a959c60ee57 100644
>>>> --- a/net/vmw_vsock/af_vsock.c
>>>> +++ b/net/vmw_vsock/af_vsock.c
>>>> @@ -1013,6 +1013,31 @@ static int vsock_getname(struct socket *sock,
>>>> return err;
>>>> }
>>>>
>>>> +void vsock_linger(struct sock *sk, long timeout)
>>>> +{
>>>> + DEFINE_WAIT_FUNC(wait, woken_wake_function);
>>>> + ssize_t (*unsent)(struct vsock_sock *vsk);
>>>> + struct vsock_sock *vsk = vsock_sk(sk);
>>>> +
>>>> + if (!timeout)
>>>> + return;
>>>> +
>>>> + /* unsent_bytes() may be unimplemented. */
>>>> + unsent = vsk->transport->unsent_bytes;
>>>> + if (!unsent)
>>>> + return;
>>>> +
>>>> + add_wait_queue(sk_sleep(sk), &wait);
>>>> +
>>>> + do {
>>>> + if (sk_wait_event(sk, &timeout, unsent(vsk) == 0, &wait))
>>>> + break;
>>>> + } while (!signal_pending(current) && timeout);
>>>> +
>>>> + remove_wait_queue(sk_sleep(sk), &wait);
>>>> +}
>>>> +EXPORT_SYMBOL_GPL(vsock_linger);
>>>> +
>>>> static int vsock_shutdown(struct socket *sock, int mode)
>>>> {
>>>> int err;
>>>> diff --git a/net/vmw_vsock/virtio_transport_common.c b/net/vmw_vsock/virtio_transport_common.c
>>>> index 4425802c5d718f65aaea425ea35886ad64e2fe6e..9230b8358ef2ac1f6e72a5961bae39f9093c8884 100644
>>>> --- a/net/vmw_vsock/virtio_transport_common.c
>>>> +++ b/net/vmw_vsock/virtio_transport_common.c
>>>> @@ -1192,27 +1192,6 @@ static void virtio_transport_remove_sock(struct vsock_sock *vsk)
>>>> vsock_remove_sock(vsk);
>>>> }
>>>>
>>>> -static void virtio_transport_wait_close(struct sock *sk, long timeout)
>>>> -{
>>>> - DEFINE_WAIT_FUNC(wait, woken_wake_function);
>>>> - ssize_t (*unsent)(struct vsock_sock *vsk);
>>>> - struct vsock_sock *vsk = vsock_sk(sk);
>>>> -
>>>> - if (!timeout)
>>>> - return;
>>>> -
>>>> - unsent = vsk->transport->unsent_bytes;
>>>> -
>>>> - add_wait_queue(sk_sleep(sk), &wait);
>>>> -
>>>> - do {
>>>> - if (sk_wait_event(sk, &timeout, unsent(vsk) == 0, &wait))
>>>> - break;
>>>> - } while (!signal_pending(current) && timeout);
>>>> -
>>>> - remove_wait_queue(sk_sleep(sk), &wait);
>>>> -}
>>>> -
>>>> static void virtio_transport_cancel_close_work(struct vsock_sock *vsk,
>>>> bool cancel_timeout)
>>>> {
>>>> @@ -1283,7 +1262,7 @@ static bool virtio_transport_close(struct vsock_sock *vsk)
>>>> (void)virtio_transport_shutdown(vsk, SHUTDOWN_MASK);
>>>>
>>>> if (sock_flag(sk, SOCK_LINGER) && !(current->flags & PF_EXITING))
>>>> - virtio_transport_wait_close(sk, sk->sk_lingertime);
>>>> + vsock_linger(sk, sk->sk_lingertime);
>>>
>>> Ah, I'd also move the check in that function, I mean:
>>>
>>> void vsock_linger(struct sock *sk) {
>>> ...
>>> if (!sock_flag(sk, SOCK_LINGER) || (current->flags & PF_EXITING))
>>> return;
>>>
>>> ...
>>> }
>>
>> One note: if we ever use vsock_linger() in vsock_shutdown(), the PF_EXITING
>> condition would be unnecessary checked for that caller, right?
>
> Right, for shutdown it should always be false, so maybe better to keep
> the check in the caller.
Or split it? Check `!sock_flag(sk, SOCK_LINGER) || !timeout` in
vsock_linger() and defer `!(flags & PF_EXITING)` to whoever does the socket
release?
next prev parent reply other threads:[~2025-04-30 11:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 9:10 [PATCH net-next v3 0/4] vsock: SOCK_LINGER rework Michal Luczaj
2025-04-30 9:10 ` [PATCH net-next v3 1/4] vsock/virtio: Linger on unsent data Michal Luczaj
2025-04-30 9:26 ` Stefano Garzarella
2025-04-30 10:28 ` Michal Luczaj
2025-04-30 9:10 ` [PATCH net-next v3 2/4] vsock/virtio: Reduce indentation in virtio_transport_wait_close() Michal Luczaj
2025-04-30 9:28 ` Stefano Garzarella
2025-04-30 10:29 ` Michal Luczaj
2025-04-30 10:34 ` Stefano Garzarella
2025-04-30 9:10 ` [PATCH net-next v3 3/4] vsock: Move lingering logic to af_vsock core Michal Luczaj
2025-04-30 9:33 ` Stefano Garzarella
2025-04-30 10:30 ` Michal Luczaj
2025-04-30 10:35 ` Stefano Garzarella
2025-04-30 9:36 ` Stefano Garzarella
2025-04-30 10:33 ` Michal Luczaj
2025-04-30 10:37 ` Stefano Garzarella
2025-04-30 11:11 ` Michal Luczaj [this message]
2025-04-30 13:50 ` Stefano Garzarella
2025-04-30 9:10 ` [PATCH net-next v3 4/4] vsock/test: Expand linger test to ensure close() does not misbehave Michal Luczaj
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=f1943412-ccbf-4913-a5c5-818f0f586db1@rbox.co \
--to=mhal@rbox.co \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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
all inboxes | Powered by JetHome®