[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220310195429.4ba93edf@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Thu, 10 Mar 2022 19:54:29 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: menglong8.dong@...il.com
Cc: dsahern@...nel.org, nhorman@...driver.com, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, kafai@...com,
songliubraving@...com, yhs@...com, john.fastabend@...il.com,
kpsingh@...nel.org, davem@...emloft.net, imagedong@...cent.com,
edumazet@...gle.com, talalahmad@...gle.com, keescook@...omium.org,
alobakin@...me, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, bpf@...r.kernel.org,
Mengen Sun <mengensun@...cent.com>,
Hao Peng <flyingpeng@...cent.com>
Subject: Re: [PATCH] net: skb: move enum skb_drop_reason to uapi
On Fri, 11 Mar 2022 11:28:28 +0800 menglong8.dong@...il.com wrote:
> From: Menglong Dong <imagedong@...cent.com>
>
> Move the definition of 'enum skb_drop_reason' in 'skbuff.h' to the uapi
> header 'net_dropmon.h', therefore some users, such as eBPF program, can
> make use of it.
BPF does not need an enum definition to be part of the uAPI to make use
of it. BTF should encode the values, and CO-RE can protect from them
changing, AFAIU. I think we need a better example user / justification.
Powered by blists - more mailing lists