All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:54:53 -0600	[thread overview]
Message-ID: <af485441-123b-4f50-f01b-cee2612b9218@gmail.com> (raw)
In-Reply-To: <20210817114402.78463d9d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On 8/17/21 12:44 PM, Jakub Kicinski wrote:
>> @kuba With PROC_NET_RAW I consider the problem is found, isn't it? So
>> I will not download/bisect<->build or otherwise investigate the
>> problem until one of you explicitely asks me to do so.
>>
>> I have now redirected invocation of command with set PROC_NET_RAW on
>> my system, and may (try to) update to Linux 4.19.
> 
> I suspect the bisection would end up at the commit which added 
> the netlink dump support, so you can hold off for now, yes.

agreed.
> 
> My best guess right now is that Knoppix has a cut-down kernel 
> config and we don't handle that case correctly.
> 

CONFIG_INET_RAW_DIAG (or INET_DIAG) is probably disabled. surprised the
netlink dump does not return an error and it falls back to the proc file:

        if (!getenv("PROC_NET_RAW") && !getenv("PROC_ROOT") &&
            inet_show_netlink(f, NULL, IPPROTO_RAW) == 0)
                return 0;

can you strace it?

  reply	other threads:[~2021-08-17 19:55 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
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 [this message]
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=af485441-123b-4f50-f01b-cee2612b9218@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 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.