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 Apr 2015 14:53:58 -0700
From:	Cong Wang <cwang@...pensource.com>
To:	Pablo Neira Ayuso <pablo@...filter.org>
Cc:	netfilter-devel@...r.kernel.org,
	David Miller <davem@...emloft.net>,
	netdev <netdev@...r.kernel.org>,
	Jamal Hadi Salim <jhs@...atatu.com>
Subject: Re: [PATCH 6/6] net: move qdisc ingress filtering on top of netfilter
 ingress hooks

On Wed, Apr 29, 2015 at 11:53 AM, Pablo Neira Ayuso <pablo@...filter.org> wrote:
> diff --git a/net/sched/Kconfig b/net/sched/Kconfig
> index 2274e72..23b57da 100644
> --- a/net/sched/Kconfig
> +++ b/net/sched/Kconfig
> @@ -312,6 +312,7 @@ config NET_SCH_PIE
>  config NET_SCH_INGRESS
>         tristate "Ingress Qdisc"
>         depends on NET_CLS_ACT
> +       select NETFILTER_INGRESS
>         ---help---
>           Say Y here if you want to use classifiers for incoming packets.
>           If unsure, say Y.


So now it impossible to compile ingress Qdics without netfilters...

(I know you moved them into net/core/, but still they are netfilter API's.)

Why do we have to mix different layers? IOW, why not just keep TC at L2
and netfilters at L3 even just w.r.t. API?
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ