Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210928194727.1635106-1-cpp.code.lv@gmail.com>
 <20210928174853.06fe8e66@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
 <d1e5b178-47f5-9791-73e9-0c1f805b0fca@6wind.com> <20210929061909.59c94eff@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
 <CAASuNyVe8z1R6xyCfSAxZbcrL3dej1n8TXXkqS-e8QvA6eWd+w@mail.gmail.com> <b091ef39-dc29-8362-4d31-0a9cc498e8ea@6wind.com>
In-Reply-To: <b091ef39-dc29-8362-4d31-0a9cc498e8ea@6wind.com>
From:   Cpp Code <cpp.code.lv@gmail.com>
Date:   Fri, 1 Oct 2021 13:42:32 -0700
Message-ID: <CAASuNyW81zpSu+FGSDuUrOsyqJj7SokZtvX081BbeXi0ARBaYg@mail.gmail.com>
Subject: Re: [PATCH net-next v6] net: openvswitch: IPv6: Add IPv6 extension
 header support
To:     Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc:     Jakub Kicinski <kuba@kernel.org>, netdev@vger.kernel.org,
        pshelar@ovn.org, "David S. Miller" <davem@davemloft.net>,
        ovs dev <dev@openvswitch.org>, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Fri, Oct 1, 2021 at 12:21 AM Nicolas Dichtel
<nicolas.dichtel@6wind.com> wrote:
>
> Le 30/09/2021 =C3=A0 18:11, Cpp Code a =C3=A9crit :
> > On Wed, Sep 29, 2021 at 6:19 AM Jakub Kicinski <kuba@kernel.org> wrote:
> >>
> >> On Wed, 29 Sep 2021 08:19:05 +0200 Nicolas Dichtel wrote:
> >>>> /* Insert a kernel only KEY_ATTR */
> >>>> #define OVS_KEY_ATTR_TUNNEL_INFO    __OVS_KEY_ATTR_MAX
> >>>> #undef OVS_KEY_ATTR_MAX
> >>>> #define OVS_KEY_ATTR_MAX            __OVS_KEY_ATTR_MAX
> >>> Following the other thread [1], this will break if a new app runs ove=
r an old
> >>> kernel.
> >>
> >> Good point.
> >>
> >>> Why not simply expose this attribute to userspace and throw an error =
if a
> >>> userspace app uses it?
> >>
> >> Does it matter if it's exposed or not? Either way the parsing policy
> >> for attrs coming from user space should have a reject for the value.
> >> (I say that not having looked at the code, so maybe I shouldn't...)
> >
> > To remove some confusion, there are some architectural nuances if we
> > want to extend code without large refactor.
> > The ovs_key_attr is defined only in kernel side. Userspace side is
> > generated from this file. As well the code can be built without kernel
> > modules.
> > The code inside OVS repository and net-next is not identical, but I
> > try to keep some consistency.
> I didn't get why OVS_KEY_ATTR_TUNNEL_INFO cannot be exposed to userspace.

OVS_KEY_ATTR_TUNNEL_INFO is compressed version of OVS_KEY_ATTR_TUNNEL
and for clarity purposes its not exposed to userspace as it will never
use it.
I would say it's a coding style as it would not brake anything if exposed.

>
> >
> > JFYI This is the file responsible for generating userspace part:
> > https://github.com/openvswitch/ovs/blob/master/build-aux/extract-odp-ne=
tlink-h
> > This is the how corresponding file for ovs_key_attr looks inside OVS:
> > https://github.com/openvswitch/ovs/blob/master/datapath/linux/compat/in=
clude/linux/openvswitch.h
> > one can see there are more values than in net-next version.
> There are still some '#ifdef __KERNEL__'. The standard 'make headers_inst=
all'
> filters them. Why not using this standard mechanism?

Could you elaborate on this, I don't quite understand the idea!? Which
ifdef you are referring, the one along OVS_KEY_ATTR_TUNNEL_INFO or
some other?

>
> In this file, there are two attributes (OVS_KEY_ATTR_PACKET_TYPE and
> OVS_KEY_ATTR_ND_EXTENSIONS) that doesn't exist in the kernel.
> This will also breaks if an old app runs over a new kernel. I don't see h=
ow it
> is possible to keep the compat between {old|new} {kernel|app}.

Looks like this most likely is a bug while working on multiple
versions of code.  Need to do add more padding.

>
>
> Regards,
> Nicolas