netdev - Re: [PATCH net-next 1/2] ebpf: add sched_act_type and map it to sk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150320142129.GF2223@nanopsycho.brq.redhat.com>
Date:	Fri, 20 Mar 2015 15:21:29 +0100
From:	Jiri Pirko <jiri@...nulli.us>
To:	Daniel Borkmann <daniel@...earbox.net>
Cc:	davem@...emloft.net, ast@...mgrid.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 1/2] ebpf: add sched_act_type and map it to
 sk_filter's verifier ops

Fri, Mar 20, 2015 at 03:11:11PM CET, daniel@...earbox.net wrote:
>In order to prepare eBPF support for tc action, we need to add
>sched_act_type, so that the eBPF verifier is aware of what helper
>function act_bpf may use, that it can load skb data and read out
>currently available skb fields.
>
>This is bascially analogous to 96be4325f443 ("ebpf: add sched_cls_type
>and map it to sk_filter's verifier ops").
>
>BPF_PROG_TYPE_SCHED_CLS and BPF_PROG_TYPE_SCHED_ACT need to be
>separate since both will have a different set of functionality in
>future (classifier vs action), thus we won't run into ABI troubles
>when the point in time comes to diverge functionality from the
>classifier.
>
>The future plan for act_bpf would be that it will be able to write
>into skb->data and alter selected fields mirrored in struct __sk_buff.
>
>For an initial support, it's sufficient to map it to sk_filter_ops.
>
>Signed-off-by: Daniel Borkmann <daniel@...earbox.net>
>Cc: Jiri Pirko <jiri@...nulli.us>

Reviewed-by: Jiri Pirko <jiri@...nulli.us>
--
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