aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorStefano Garzarella <sgarzare@redhat.com>2021-04-16 12:44:16 +0200
committerDavid S. Miller <davem@davemloft.net>2021-04-19 14:30:23 -0700
commite16edc99d658cd41c60a44cc14d170697aa3271f (patch)
tree8f7c6ee297109b2a292b1c96c66266a19dd46cb2 /tools/perf/scripts/python/export-to-postgresql.py
parentMerge tag 'net-5.12-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (diff)
downloadwireguard-linux-e16edc99d658cd41c60a44cc14d170697aa3271f.tar.xz
wireguard-linux-e16edc99d658cd41c60a44cc14d170697aa3271f.zip
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>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions