Re: Re: [Patch net 1/2] vsock/virtio: initialize rx_buf_nr and rx_buf_max_nr when resuming

>You need to update the title now that you're moving also queued_replies. > Well, I will update the title in V3 version. >On Tue, Feb 11, 2025 at 03:19:21PM +0800, Junnan Wu wrote: >>When executing suspend to ram twice in a row, >>the `rx_buf_nr` and `rx_buf_max_nr`

RE: Re: [PATCH 2/2] vsock/virtio: Don't reset the created SOCKET during s2r

b 07, 2025 at 01:20:33PM +0800, Junnan Wu wrote: >>>From: Ying Gao >>> >>>If suspend is executed during vsock communication and the >>>socket is reset, the original socket will be unusable after resume. > >Why? (I mean for a good commit description) > >

[Patch net 1/2] vsock/virtio: initialize rx_buf_nr and rx_buf_max_nr when resuming

off-by: Ying Gao Signed-off-by: Junnan Wu --- net/vmw_vsock/virtio_transport.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/net/vmw_vsock/virtio_transport.c b/net/vmw_vsock/virtio_transport.c index b58c3818f284..f0e48e6911fc 100644 --- a/net/vmw_vsock/virtio_trans

[Patch net 2/2] vsock/virtio: Don't reset the created SOCKET during suspend to ram

the 2 use cases. Co-developed-by: Ying Gao Signed-off-by: Ying Gao Signed-off-by: Junnan Wu --- net/vmw_vsock/virtio_transport.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/net/vmw_vsock/virtio_transport.c b/net/vmw_vsock/virtio_transport.c index

[Patch net 0/2] vsock suspend/resume fix

CC all maintainers and reviews. Modify commits accroding to reviewers' comments. Re-organize the patches, cover letter, tag, Signed-Off, Co-worker etc. Junnan Wu (2): vsock/virtio: initialize rx_buf_nr and rx_buf_max_nr when resuming vsock/virtio: Don't reset the created SOCKET duri