netdev - Re: [PATCH net v2 2/3] taprio: Allow users not to specify "flags" when changing schedules

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:   Wed, 29 Jan 2020 14:23:10 +0200
From:   Vladimir Oltean <olteanv@...il.com>
To:     David Miller <davem@...emloft.net>
Cc:     Vinicius Costa Gomes <vinicius.gomes@...el.com>,
        netdev <netdev@...r.kernel.org>,
        Jamal Hadi Salim <jhs@...atatu.com>,
        Cong Wang <xiyou.wangcong@...il.com>,
        Jiri Pirko <jiri@...nulli.us>,
        Vladimir Oltean <vladimir.oltean@....com>,
        Po Liu <po.liu@....com>
Subject: Re: [PATCH net v2 2/3] taprio: Allow users not to specify "flags"
 when changing schedules

On Wed, 29 Jan 2020 at 14:10, David Miller <davem@...emloft.net> wrote:
>
> From: Vladimir Oltean <olteanv@...il.com>
> Date: Wed, 29 Jan 2020 13:24:30 +0200
>
> > At some point, the 5.3 kernel will go EOL. When would be a good time
> > to make the "flags" optional on "tc qdisc replace", without concerns
> > about different behavior across versions?
>
> 5.3, and 5.4, and... and how long do distros ship that kernel?
>
> This is why it is absolutely critical to flesh out all public
> facing interface concerns before the feature is merged into
> the tree rather than later.

So the answer to "when would be a good time" is "never"?

-Vladimir