netdev - Re: [PATCH 6/6] net: move qdisc ingress filtering on top of netfilter ingress hooks

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]

Message-ID: <20150430040535.GH8950@acer.localdomain>
Date:	Thu, 30 Apr 2015 06:05:37 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	Jamal Hadi Salim <jhs@...atatu.com>
Cc:	Daniel Borkmann <daniel@...earbox.net>,
	Pablo Neira Ayuso <pablo@...filter.org>,
	netfilter-devel@...r.kernel.org, davem@...emloft.net,
	netdev@...r.kernel.org
Subject: Re: [PATCH 6/6] net: move qdisc ingress filtering on top of
 netfilter ingress hooks

On 30.04, Patrick McHardy wrote:
> Regarding TC as a whole, I think the problem is shared between userspace
> and the kernel. iproute TC is certainly completely failed, its unusable
> without looking at the kernel and iproute code, it hasn't even made the
> slightest infrastructrual progess in the past 15 years (*(u16)RTN_DATA(bla))?)
> and that is telling for itself. I don't extend that to ip, even though it
> suffers from the same coding problems, but let's be honest, do you really
> expect some magic is going to happen and TC userspace will suddenly become
> usable?
> 
> I don't. And we intend to provide an alternative.

For the sake of completeness - on ingress, this alternativ means simply
ditching TC. On egress, we will provide a nicely integrated way of qdiscs
and classifiers where nftables will obviously respect the qdiscs. On
ingress, there is simply no benefit in doing that at all. Hence Pablo's
patches.
--
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