netdev - Re: [PATCH iproute2] vxlan: add support for flowlab inherit

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Mon, 22 Jan 2024 17:29:29 -0700
From: David Ahern <dsahern@...il.com>
To: Stephen Hemminger <stephen@...workplumber.org>,
 Vincent Bernat <vincent@...nat.ch>
Cc: Ido Schimmel <idosch@...sch.org>, Alce Lafranque <alce@...ranque.net>,
 netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] vxlan: add support for flowlab inherit

On 1/22/24 5:10 PM, Stephen Hemminger wrote:
> On Mon, 22 Jan 2024 22:11:32 +0100
> Vincent Bernat <vincent@...nat.ch> wrote:
> 
>> On 2024-01-22 13:24, Ido Schimmel wrote:
>>> s/flowlab/flowlabel/ in subject
>>>
>>> My understanding is that new features should be targeted at
>>> iproute2-next. See the README.  
>>
>> You may be more familiar than I am about this, but since the kernel part 
>> is already in net, it should go to the stable branch of iproute2.
> 
> There is no stable branch. Only current (based of Linus tree)
> and next (for net-next kernel).

to expand: iproute2 follows the netdev model which means -main is for
bug fixes, and -next is for new features.

If a new kernel feature needs support in iproute2, then the patch to
iproute2 needs to be sent during the same development window as the
kernel support. New feature support will not be added to -main branch
regardless of when the kernel side landed.