netdev - Re: [PATCH] retain ABI definitions for obsolete multi-queue packet schedulers

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:	Fri, 12 Sep 2008 16:01:54 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	shemminger@...tta.com
Cc:	kaber@...sh.net, netdev@...r.kernel.org
Subject: Re: [PATCH] retain ABI definitions for obsolete multi-queue packet
 schedulers

From: Stephen Hemminger <shemminger@...tta.com>
Date: Fri, 12 Sep 2008 15:58:30 -0700

> On Fri, 12 Sep 2008 15:30:33 -0700 (PDT)
> David Miller <davem@...emloft.net> wrote:
> 
> > From: Stephen Hemminger <shemminger@...tta.com>
> > Date: Fri, 12 Sep 2008 12:25:48 -0700
> > 
> > > On Fri, 12 Sep 2008 10:00:11 -0700
> > > Stephen Hemminger <shemminger@...tta.com> wrote:
> > > 
> > > > Even though the sch_rr qdisc is now gone in 2.6.27, the kernel
> > > > definitions for the attributes need to be maintained because applications
> > > > like iproute need to be compatible with older kernels and use santized
> > > > kernel headers.
> >  ...
> > > This should be applied for 2.6.27 since it is a build regression.
> > 
> > You use a local copy of this header file in iproute2, you don't even
> > use the kernel header itself.  It's the worst possible example and
> > excuse for this change.
> > 
> > Nobody references this header directly for these definitions.
> > The one and only use is using a local copy.
> > 
> > iproute2 is the only thing even remotely referencing this stuff.
> > 
> > So there is no breakage.  The only breakage is if you, Stephen, decide
> > to copy the kernel header into iproute2 as-is, and that is your
> > choice.  :-)
> 
> Every release I copy the sanitized kernel headers resulting
> from 'make headers_install'.  That is how they have been maintained and
> up until now it worked.  The sch_rr configuration portion was referencing
> this.  The point of the sanitized headers was to avoid this nonsense.

But here is the flip side, we actually don't want new applications
referencing those things, since no kernel from now and into the
future will ever support those knobs again.  They will always fail.

Therefore, it makes sense to put the definitions into the one existing
tool that used it.  You can even put those defines directly into the
sch_rr iproute2 code, and then your sanitized header bits will
continue to work transparently.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html