vsock/test: Do not filter kallsyms by symbol type
[ Upstream commit 5d54aa40c7b7e9dee5746cca99e9ddbcca13e895 ]
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: 3070c05b7a ("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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
parent
902fd1026c
commit
9eb4e2396c
|
|
@ -25,7 +25,7 @@ enum transport {
|
|||
};
|
||||
|
||||
static const char * const transport_ksyms[] = {
|
||||
#define x(name, symbol) "d " symbol "_transport",
|
||||
#define x(name, symbol) " " symbol "_transport",
|
||||
KNOWN_TRANSPORTS(x)
|
||||
#undef x
|
||||
};
|
||||
|
|
|
|||
Loading…
Reference in New Issue