| 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
| ||
|
Date: Wed, 17 Jul 2019 06:45:05 -0700 From: Dave Taht <dave.taht@...il.com> To: Loganaden Velvindron <loganaden@...il.com> Cc: netdev <netdev@...r.kernel.org> Subject: Re: Request for backport of 96125bf9985a75db00496dd2bc9249b777d2b19b On Mon, Jul 15, 2019 at 11:01 AM Loganaden Velvindron <loganaden@...il.com> wrote: > > On Fri, Jul 5, 2019 at 6:15 PM Loganaden Velvindron <loganaden@...il.com> wrote: > > > > Hi folks, > > > > I read the guidelines for LTS/stable. > > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > > > > > > Although this is not a bugfix, I am humbly submitting a request so > > that commit id > > -- 96125bf9985a75db00496dd2bc9249b777d2b19b Allow 0.0.0.0/8 as a valid > > address range -- is backported to all LTS kernels. > > > > My motivation for such a request is that we need this patch to be as > > widely deployed as possible and as early as possible for interop and > > hopefully move into better utilization of ipv4 addresses space. Hence > > my request for it be added to -stable. > > > > Any feedback ? > > > Kind regards, > > //Logan I am perfectly willing to wait a year or so on the -stable front to see what, if any, problems that ensue from mainlining this in 5.3. It's straightforward for distros that wish to do this backport (like openwrt) to do it now, and other OSes will take longer than this to adopt, regardless. -- Dave Täht CTO, TekLibre, LLC http://www.teklibre.com Tel: 1-831-205-9740
Powered by blists - more mailing lists