vsock/vmci: log once the failed queue pair allocation
BugLink: https://bugs.launchpad.net/bugs/1929615 [ Upstream commite16edc99d6
] 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 commite8266c4c33
("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:d021c34405
("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> Signed-off-by: Sasha Levin <sashal@kernel.org> Signed-off-by: Kamal Mostafa <kamal@canonical.com> Signed-off-by: Kleber Sacilotto de Souza <kleber.souza@canonical.com>
This commit is contained in:
parent
aabedb30e2
commit
6d072acdb8
|
@ -576,8 +576,7 @@ vmci_transport_queue_pair_alloc(struct vmci_qp **qpair,
|
|||
peer, flags, VMCI_NO_PRIVILEGE_FLAGS);
|
||||
out:
|
||||
if (err < 0) {
|
||||
pr_err("Could not attach to queue pair with %d\n",
|
||||
err);
|
||||
pr_err_once("Could not attach to queue pair with %d\n", err);
|
||||
err = vmci_transport_error_to_vsock_error(err);
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue