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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 25 Jan 2020 20:54:45 -0800 From: Alexei Starovoitov <alexei.starovoitov@...il.com> To: David Ahern <dsahern@...il.com> Cc: Toke Høiland-Jørgensen <toke@...hat.com>, Jakub Kicinski <kuba@...nel.org>, David Ahern <dsahern@...nel.org>, netdev@...r.kernel.org, prashantbhole.linux@...il.com, jasowang@...hat.com, davem@...emloft.net, jbrouer@...hat.com, mst@...hat.com, toshiaki.makita1@...il.com, daniel@...earbox.net, john.fastabend@...il.com, ast@...nel.org, kafai@...com, songliubraving@...com, yhs@...com, andriin@...com, David Ahern <dahern@...italocean.com> Subject: Re: [PATCH bpf-next 03/12] net: Add IFLA_XDP_EGRESS for XDP programs in the egress path On Sat, Jan 25, 2020 at 06:43:36PM -0700, David Ahern wrote: > > That said, Martin's comment throws a wrench in the goal: if the existing > code does not enforce expected_attach_type then that option can not be > used in which case I guess I have to go with a new program type > (BPF_PROG_TYPE_XDP_EGRESS) which takes a new context (xdp_egress_md), > has different return codes, etc. This is acceptable risk. We did such thing in the past. The chances of user space breakage are extremely low.
Powered by blists - more mailing lists