vsock/vmci: log once the failed queue pair allocation
authorStefano Garzarella <sgarzare@redhat.com>
Fri, 16 Apr 2021 10:44:16 +0000 (12:44 +0200)
committerDavid S. Miller <davem@davemloft.net>
Mon, 19 Apr 2021 21:30:23 +0000 (14:30 -0700)
commite16edc99d658cd41c60a44cc14d170697aa3271f
tree8f7c6ee297109b2a292b1c96c66266a19dd46cb2
parent88a5af943985fb43b4c9472b5abd9c0b9705533d
vsock/vmci: log once the failed queue pair allocation

VMCI feature is not supported in conjunction with the vSphere Fault
Tolerance (FT) feature.

VMware Tools can repeatedly try to create a vsock connection. If FT is
enabled the kernel logs is flooded with the following messages:

    qp_alloc_hypercall result = -20
    Could not attach to queue pair with -20

"qp_alloc_hypercall result = -20" was hidden by commit e8266c4c3307
("VMCI: Stop log spew when qp allocation isn't possible"), but "Could
not attach to queue pair with -20" is still there flooding the log.

Since the error message can be useful in some cases, print it only once.

Fixes: d021c344051a ("VSOCK: Introduce VM Sockets")
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
Reviewed-by: Jorgen Hansen <jhansen@vmware.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/vmw_vsock/vmci_transport.c