[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240703172039.55658e68@kernel.org>
Date: Wed, 3 Jul 2024 17:20:39 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: Asbjørn Sloth Tønnesen
<ast@...erby.net>, <netdev@...r.kernel.org>, Davide Caratti
<dcaratti@...hat.com>, "Ilya Maximets" <i.maximets@....org>, Jamal Hadi
Salim <jhs@...atatu.com>, Cong Wang <xiyou.wangcong@...il.com>, Jiri Pirko
<jiri@...nulli.us>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, David Ahern
<dsahern@...nel.org>, Simon Horman <horms@...nel.org>, Ratheesh Kannoth
<rkannoth@...vell.com>, Florian Westphal <fw@...len.de>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 1/9] net/sched: flower: define new tunnel flags
On Wed, 3 Jul 2024 12:59:54 +0200 Alexander Lobakin wrote:
> > enum {
> > TCA_FLOWER_KEY_FLAGS_IS_FRAGMENT = (1 << 0),
> > TCA_FLOWER_KEY_FLAGS_FRAG_IS_FIRST = (1 << 1),
> > + /* FLOW_DIS_ENCAPSULATION (1 << 2) is not exposed to userspace */
>
> Should uAPI header contain this comment? FLOW_DIS_ENCAPSULATION is an
> internal kernel definition, so I believe its name shouldn't leak to the
> userspace header.
Also since it's internal, can avoid the gap in uAPI and make
ENCAPSULATION be something like "last uAPI bit + 1" ?
Powered by blists - more mailing lists