Displaying 5 results from an estimated 5 matches for "vsock_connect".
Did you mean:
sock_connect
2023 Mar 26
0
[syzbot] [net?] [virt?] [io-uring?] [kvm?] BUG: soft lockup in vsock_connect
On Sat, Mar 18, 2023 at 12:32:39AM +0000, Bobby Eshleman wrote:
> On Fri, Mar 24, 2023 at 09:38:38AM +0100, Stefano Garzarella wrote:
> > Hi Bobby,
> > FYI we have also this one, but it seems related to
> > syzbot+befff0a9536049e7902e at syzkaller.appspotmail.com
> >
> > Thanks,
> > Stefano
> >
>
> Got it, I'll look into it.
>
It seems
2023 Mar 27
0
[syzbot] [net?] [virt?] [io-uring?] [kvm?] BUG: soft lockup in vsock_connect
On Sat, Mar 25, 2023 at 1:44?AM Bobby Eshleman <bobbyeshleman at gmail.com> wrote:
>
> On Fri, Mar 24, 2023 at 09:38:38AM +0100, Stefano Garzarella wrote:
> > Hi Bobby,
> > FYI we have also this one, but it seems related to
> > syzbot+befff0a9536049e7902e at syzkaller.appspotmail.com
> >
> > Thanks,
> > Stefano
> >
>
> Got it, I'll
2023 May 10
0
[PATCH] vsock: bugfix port residue in server
...directly set the state of this vsock
>to CLOSE and return ETIMEDOUT, User will release the port. It will not
What to you mean with "User" here?
>notify the server when the port is released, causing the server port remain
>
Can we remove this blank line?
>when client's vsock_connect timeout?it should check sk state is
The remote peer can't trust the other peer, indeed it will receive an
error after sending the first message and it will remove the connection,
right?
>ESTABLISHED or not. if sk state is ESTABLISHED, it means the connection
>is established, the client...
2023 May 11
0
[PATCH net v2] vsock: avoid to close connected socket after the timeout
...tablished. However, the client's timer also times out, the original
>processing logic of the client is to directly set the state of this vsock
>to CLOSE and return ETIMEDOUT. It will not notify the server when the port
>is released, causing the server port remain.
>when client's vsock_connect timeout?it should check sk state is
>ESTABLISHED or not. if sk state is ESTABLISHED, it means the connection
>is established, the client should not set the sk state to CLOSE
>
>Note: I encountered this issue on kernel-4.18, which can be fixed by
>this patch. Then I checked the latest...
2023 May 30
1
[syzbot] [kvm?] [net?] [virt?] general protection fault in vhost_work_queue
...0000000400
> Call Trace:
> <TASK>
> vhost_transport_send_pkt+0x268/0x520 drivers/vhost/vsock.c:288
> virtio_transport_send_pkt_info+0x54c/0x820 net/vmw_vsock/virtio_transport_common.c:250
> virtio_transport_connect+0xb1/0xf0 net/vmw_vsock/virtio_transport_common.c:813
> vsock_connect+0x37f/0xcd0 net/vmw_vsock/af_vsock.c:1414
> __sys_connect_file+0x153/0x1a0 net/socket.c:2003
> __sys_connect+0x165/0x1a0 net/socket.c:2020
> __do_sys_connect net/socket.c:2030 [inline]
> __se_sys_connect net/socket.c:2027 [inline]
> __x64_sys_connect+0x73/0xb0 net/socket.c:2027...