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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM0EoMmfkjFvD9hyaQryEn-RFyfAiYBDCKpJXr3uZpQ=PTA5tA@mail.gmail.com>
Date:   Tue, 14 Feb 2023 09:01:32 -0500
From:   Jamal Hadi Salim <jhs@...atatu.com>
To:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Cc:     Cong Wang <xiyou.wangcong@...il.com>,
        Jiri Pirko <jiri@...nulli.us>,
        David Miller <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Stephen Hemminger <stephen@...workplumber.org>,
        David Ahern <dsahern@...il.com>
Subject: iproute2/user space code obsoletion when depending on kernel features
 WAS([PATCH net-next 0/5] net/sched: Retire some tc qdiscs and classifiers)

Refer to: https://lore.kernel.org/netdev/20230214134915.199004-1-jhs@mojatatu.com/T/#t

I dont believe this has been done before so some introspection is needed.
The option seem to be:
1) Delete it from the iproute2 version that maps to a kernel version
2) Keep it around and dont bother syncing specific kernel headers in
the next version. This would allow newer iproute2 to continue
supporting older kernels.
Additionally, add an ominous message saying that the feature is no
longer supported in newer kernels.

cheers,
jamal

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ