From: Luigi Leonardi <leonardi@redhat.com>
To: sgarzare@redhat.com, stefanha@redhat.com, netdev@vger.kernel.org
Cc: Luigi Leonardi <leonardi@redhat.com>
Subject: [PATCH iproute2] ss: fix vsock port filter
Date: Tue, 21 Apr 2026 14:35:12 +0200 [thread overview]
Message-ID: <20260421-fix_vsock-v1-1-812c80a76c1a@redhat.com> (raw)
parse_hostcond() uses get_u32() to parse the vsock port into the
aafilter.port field, which is a long. On 64-bit systems, get_u32()
only writes the lower 32 bits, leaving the upper 32 bits set from
the -1 initialization. This causes the port comparison
"a->port != s->rport" in run_ssfilter() to always fail, since the
corrupted long value never matches the int rport.
Fix by using get_long() instead, consistent with how AF_PACKET and
AF_NETLINK handle the same field.
Fixes: c759116a0b2b ("ss: add AF_VSOCK support")
Signed-off-by: Luigi Leonardi <leonardi@redhat.com>
---
misc/ss.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/misc/ss.c b/misc/ss.c
index 14e9f27a..6e3321ac 100644
--- a/misc/ss.c
+++ b/misc/ss.c
@@ -2323,7 +2323,7 @@ void *parse_hostcond(char *addr, bool is_port)
port = find_port(addr, is_port);
if (port && strcmp(port, "*") &&
- get_u32((__u32 *)&a.port, port, 0))
+ get_long(&a.port, port, 0))
return NULL;
if (!is_port && addr[0] && strcmp(addr, "*")) {
---
base-commit: e0517e612199cacaf2dc4d54cbed52deec640c94
change-id: 20260421-fix_vsock-40c2ef4928aa
Best regards,
--
Luigi Leonardi <leonardi@redhat.com>
next reply other threads:[~2026-04-21 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 12:35 Luigi Leonardi [this message]
2026-04-21 14:01 ` [PATCH iproute2] ss: fix vsock port filter Luigi Leonardi
2026-04-21 14:07 ` Stefano Garzarella
2026-04-21 16:03 ` Luigi Leonardi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260421-fix_vsock-v1-1-812c80a76c1a@redhat.com \
--to=leonardi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox