All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Luigi Leonardi <leonardi@redhat.com>
Cc: sgarzare@redhat.com, stefanha@redhat.com, netdev@vger.kernel.org,
	stephen@networkplumber.org
Subject: Re: [PATCH iproute2 v2 0/2] ss: fix vsock port filtering
Date: Tue, 25 Aug 2026 04:10:13 +0000	[thread overview]
Message-ID: <178763101313.3232246.1112979804356427442.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260817-fix_vsock-v2-0-47e544221eae@redhat.com>

Hello:

This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Mon, 17 Aug 2026 14:54:19 +0200 you wrote:
> Vsock port filtering is broken for ports in [1, 2^31−1] (i.e. any port
> whose u32 representation has bit 31 clear, which includes all ordinarily
> assigned vsock ports).
> 
> To reproduce:
> 
>     ncat -l --vsock -p 27354
>     ss --vsock -l src :27354   # shows nothing
> 
> [...]

Here is the summary with links:
  - [iproute2,v2,1/2] ss: move lport and rport in struct sockstat from int to long
    (no matching commit)
  - [iproute2,v2,2/2] ss: fix vsock port filter
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=8016d5a12e6c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-25  4:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 12:54 [PATCH iproute2 v2 0/2] ss: fix vsock port filtering Luigi Leonardi
2026-08-17 12:54 ` [PATCH iproute2 v2 1/2] ss: move lport and rport in struct sockstat from int to long Luigi Leonardi
2026-08-25  4:16   ` Stephen Hemminger
2026-08-17 12:54 ` [PATCH iproute2 v2 2/2] ss: fix vsock port filter Luigi Leonardi
2026-08-25  4:10 ` patchwork-bot+netdevbpf [this message]

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=178763101313.3232246.1112979804356427442.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=leonardi@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=stephen@networkplumber.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.