[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170427.120019.1559603500876505216.davem@davemloft.net>
Date: Thu, 27 Apr 2017 12:00:19 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: hannes@...essinduktion.org
Cc: daniel@...earbox.net, netdev@...r.kernel.org, ast@...nel.org,
daniel@...earbox.com, jbenc@...hat.com, aconole@...heb.org
Subject: Re: [PATCH net-next 6/6] bpf: show bpf programs
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
Date: Thu, 27 Apr 2017 15:22:49 +0200
> Sure, that sounds super. But so far Linux and most (maybe I should write
> all) subsystems always provided some easy way to get the insights of the
> kernel without having to code or rely on special tools so far.
Not true.
You cannot fully dump socket TCP internal state without netlink based
tools. It is just one of many examples.
Can you dump all nftables rules without a special tool?
I don't think this is a legitimate line of argument, and I want
this to be done via the bpf() system call which is what people
are working on.
Thanks.
Powered by blists - more mailing lists