netdev - Re: [patch net-next v2 0/5] Refactor IP defragmentation and fragmenation APIs for OVS conntrack support

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] [day] [month] [year] [list]

Message-Id: <20150311.164550.2247000676434784013.davem@davemloft.net>
Date:	Wed, 11 Mar 2015 16:45:50 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	azhou@...ira.com
Cc:	netdev@...r.kernel.org
Subject: Re: [patch net-next v2 0/5] Refactor IP defragmentation and
 fragmenation APIs for OVS conntrack support

From: Andy Zhou <azhou@...ira.com>
Date: Tue, 10 Mar 2015 12:07:13 -0700

> These are the patches refactors the core APIs for both IPv4 and IPv6.
> 
> The intended use for openvswitch has been posted in the eariler RFC:
> 
> http://lists.openwall.net/netdev/2015/03/02/220

Yet another hack for openvswitch.

I'm tired of this frankenstein subsystem deciding what the invariants
actually are for our core APIs.

It is completely natural to expect that there is some device to
interrogate regarding link layer capabilities, such as MTU.

And it is openvswitch's problem that they decided to break this
invariant.

I'm not accepting hacks in ipv4/ipv6 to workaround a mistake that
the OVS folks decided to make, sorry.

Stop making OVS such a damn mess, please.
--
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