From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, Jonas Bechtel <post@jbechtel.de>
Cc: netdev@vger.kernel.org
Subject: Re: ss command not showing raw sockets? (regression)
Date: Tue, 17 Aug 2021 08:57:10 -0600 [thread overview]
Message-ID: <1dafd125-cd9f-f05c-a133-80d72b2fe99b@gmail.com> (raw)
In-Reply-To: <20210816150800.28ef2e7c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On 8/16/21 4:08 PM, Jakub Kicinski wrote:
> On Sun, 15 Aug 2021 23:17:38 +0200 Jonas Bechtel wrote:
>> I've got following installation:
>> * ping 32 bit version
>> * Linux 4.4.0 x86_64 (yes, somewhat ancient)
>> * iproute2 4.9.0 or 4.20.0 or 5.10.0
>>
>> With one ping command active, there are two raw sockets on my system:
>> one for IPv4 and one for IPv6 (just one of those is used).
>>
>> My problem is that
>>
>> ss -awp
>>
>> shows
>> * two raw sockets (4.9.0)
>> * any raw socket = bug (4.20.0)
>> * any raw socket = bug (5.10.0)
>
> Could you clarify how the bug manifests itself? Does ss crash?
I take it kernel version is constant and iproute2 version changes,
correct? Can you download the source and do a git bisect?
>
>> So is this a bug or is this wont-fix (then, if it is related to
>> kernel version, package maintainers may be interested)?
next prev parent reply other threads:[~2021-08-17 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 21:17 ss command not showing raw sockets? (regression) Jonas Bechtel
2021-08-16 22:08 ` Jakub Kicinski
2021-08-17 14:57 ` David Ahern [this message]
2021-08-17 15:04 ` Jakub Kicinski
2021-08-17 18:21 ` Jonas Bechtel
2021-08-17 18:44 ` Jakub Kicinski
2021-08-17 19:54 ` David Ahern
2021-08-17 21:37 ` Jakub Kicinski
2021-08-18 0:47 ` David Ahern
2021-08-18 19:57 ` Jonas Bechtel
2021-08-18 20:43 ` David Ahern
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=1dafd125-cd9f-f05c-a133-80d72b2fe99b@gmail.com \
--to=dsahern@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=post@jbechtel.de \
/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).