[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1427934556.1892386.248333013.431CD73B@webmail.messagingengine.com>
Date: Thu, 02 Apr 2015 02:29:16 +0200
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
To: Daniel Borkmann <daniel@...earbox.net>, stephen@...workplumber.org
Cc: ast@...mgrid.com, jiri@...nulli.us, tgraf@...g.ch,
netdev@...r.kernel.org, Jamal Hadi Salim <jhs@...atatu.com>
Subject: Re: [PATCH iproute2 -next] tc,
bpf: finalize eBPF support for cls and act front-end
Hey Daniel,
On Thu, Apr 2, 2015, at 02:24, Daniel Borkmann wrote:
> On 04/02/2015 02:13 AM, Hannes Frederic Sowa wrote:
> ...
> > Maybe a small utility programs like:
> >
> > bpf (--lookup|--update|--delete|--get-next-key) -fd
> > filedescriptor-number (type conversion parameters here) key [value]
> >
> > So it can be easily used by shell scripts.
> >
> > For that the filedescriptor numbers would need to be exported (already
> > opened) into a spawned shell and the numbers could be specified either
> > in environment or just by printing text which can be sourced by shells
> > (we already talked about the maybe exec 5</proc/pid/fd/1234 idea). Seems
> > this can be just build ontop this current patch by extending the
> > bpf-agent you already build, no?
>
> I was thinking about that and trying it out, but as far as I can tell,
> due to the anon inodes that are currently underlying as the fd provider,
> it doesn't work w/o larger kernel changes. So, the file descriptor
> passing
> is currently the only way to transfer control.
Does receiving them via af_unix and spawning a new shell with the fds
already open work?
Bye,
Hannes
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists