From: Vadim Kochan <vadim4j@gmail.com>
To: Mihai Moldovan <ionic@ionic.de>
Cc: netdev@vger.kernel.org
Subject: Re: iproute2 regression -- ss -u returns an empty list
Date: Tue, 28 Apr 2015 14:21:08 +0300 [thread overview]
Message-ID: <20150428112108.GA22108@angus-think.wlc.globallogic.com> (raw)
In-Reply-To: <553EE0D9.3050601@ionic.de>
On Tue, Apr 28, 2015 at 03:22:33AM +0200, Mihai Moldovan wrote:
> Hi,
>
> Following up a bug report I received at
> http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=799 it looks like the current
> version iproute2's ss utility always returns an empty result set whenever
> specifying the -u flag.
>
> The problem has been bisected to 9db7bf15e22b6a1b8bc09c4a1e29571cbca55c94 and is
> also affecting version 3.19.0, but most notably 4.0.0+.
>
> I'm not quite sure that's the correct commit, but it does definitely look related.
>
> Even ss -xu, which previously returned a list of UNIX and UDP sockets now
> returns nothing on my systems.
>
>
> Any help with that matter is greatly appreciated.
>
>
>
> Mihai
>
Hi Mihai,
Seems I have a fixed version, I tested it localy with different
option combinations, and now there should be no issues when specifying
different families.
Would you be able to test it ? How I can provide a fixed version to you -
by patch or I can push to my github and give you a link ?
Thanks,
next prev parent reply other threads:[~2015-04-28 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 1:22 iproute2 regression -- ss -u returns an empty list Mihai Moldovan
[not found] ` <20150428040516.GA14129@angus-think.lan>
2015-04-28 4:33 ` Mihai Moldovan
2015-04-28 4:47 ` Vadim Kochan
2015-04-28 5:07 ` Mihai Moldovan
2015-04-28 5:11 ` Vadim Kochan
2015-04-28 11:21 ` Vadim Kochan [this message]
2015-04-28 13:14 ` Mihai Moldovan
2015-04-29 9:46 ` Vadim Kochan
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=20150428112108.GA22108@angus-think.wlc.globallogic.com \
--to=vadim4j@gmail.com \
--cc=ionic@ionic.de \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).