On Fri, Nov 13, 2020 at 3:28 PM Eelco Chaudron <[email protected]> wrote: > > It is already in the mainline kernel, so changing it now would break the > UAPI. Don't think this is allowed from the kernel side. > > > What I'm suggesting is to send a bugfix to kernel > > to accept only format with nested OVS_DEC_TTL_ATTR_ACTION. Since this > > feature was never implemented in userspace OVS, this change will not > > break anything. On the OVS side we should always format netlink > > messages > > in a correct way. We have a code that checks feature existence in > > kernel > > and it should fail if kernel is broken (as it is right now). In this > > case > > OVS will continue to use old implementation with setting the ttl > > field. > > > > Since the patch for a kernel is a bug fix, it should be likely > > backported > > to stable versions, and distributions will pick it up too. > > If the kernel UAPI breakage is not a problem, I think this would work. > > > Thoughts? > > > > Best regards, Ilya Maximets. >
Who is the only user of the kernel dec_ttl action now? I guess that only a patched vswitchd will, unless someone tries to program the datapath by hand. Cheers, -- per aspera ad upstream _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
