From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] bpf: add show_fdinfo handler for maps
Date: Thu, 19 Nov 2015 10:32:41 -0800 [thread overview]
Message-ID: <20151119183240.GA5993@ast-mbp.thefacebook.com> (raw)
In-Reply-To: <1447957164.2292053.444566657.27F336C7@webmail.messagingengine.com>
On Thu, Nov 19, 2015 at 07:19:24PM +0100, Hannes Frederic Sowa wrote:
> On Thu, Nov 19, 2015, at 11:56, Daniel Borkmann wrote:
> > Add a handler for show_fdinfo() to be used by the anon-inodes
> > backend for eBPF maps, and dump the map specification there. Not
> > only useful for admins, but also it provides a minimal way to
> > compare specs from ELF vs pinned object.
> >
> > Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
>
> Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
>
> Does it make sense to include bpf_htab->count in case of a hashmap?
no. user space should not rely on such things. It can only be misused.
next prev parent reply other threads:[~2015-11-19 18:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 10:56 [PATCH net-next] bpf: add show_fdinfo handler for maps Daniel Borkmann
2015-11-19 17:42 ` Alexei Starovoitov
2015-11-19 18:19 ` Hannes Frederic Sowa
2015-11-19 18:32 ` Alexei Starovoitov [this message]
2015-11-19 20:12 ` Hannes Frederic Sowa
2015-11-20 3:30 ` Alexei Starovoitov
2015-11-20 10:30 ` Hannes Frederic Sowa
2015-11-21 23:18 ` Alexei Starovoitov
2015-11-23 16:11 ` Hannes Frederic Sowa
2015-11-23 18:03 ` Alexei Starovoitov
2015-11-23 19:09 ` John Fastabend
2015-11-23 19:12 ` Hannes Frederic Sowa
2015-11-23 19:18 ` John Fastabend
2015-11-19 18:36 ` Daniel Borkmann
2015-11-19 18:45 ` Alexei Starovoitov
2015-11-20 16:04 ` David Miller
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=20151119183240.GA5993@ast-mbp.thefacebook.com \
--to=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--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).