summaryrefslogtreecommitdiff
path: root/include/linux/firmware/intel/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorMichal Luczaj <mhal@rbox.co>2026-01-16 09:52:36 +0100
committerPaolo Abeni <pabeni@redhat.com>2026-01-20 16:45:39 +0100
commit5d54aa40c7b7e9dee5746cca99e9ddbcca13e895 (patch)
tree16f9536893c53569314843ab3cfc80326a27b37f /include/linux/firmware/intel/git@git.tavy.me:linux.git
parent58bae918d73e3b6cd57d1e39fcf7c75c7dd1a8fe (diff)
vsock/test: Do not filter kallsyms by symbol type
Blamed commit implemented logic to discover available vsock transports by grepping /proc/kallsyms for known symbols. It incorrectly filtered entries by type 'd'. For some kernel configs having CONFIG_VIRTIO_VSOCKETS=m CONFIG_VSOCKETS_LOOPBACK=y kallsyms reports 0000000000000000 d virtio_transport [vmw_vsock_virtio_transport] 0000000000000000 t loopback_transport Overzealous filtering might have affected vsock test suit, resulting in insufficient/misleading testing. Do not filter symbols by type. It never helped much. Fixes: 3070c05b7afd ("vsock/test: Introduce get_transports()") Signed-off-by: Michal Luczaj <mhal@rbox.co> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com> Link: https://patch.msgid.link/20260116-vsock_test-kallsyms-grep-v1-1-3320bc3346f2@rbox.co Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'include/linux/firmware/intel/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions