| 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
| ||
|
Message-ID: <20141016055247.GA13475@casper.infradead.org> Date: Thu, 16 Oct 2014 06:52:47 +0100 From: Thomas Graf <tgraf@...g.ch> To: David Miller <davem@...emloft.net> Cc: dborkman@...hat.com, luto@...capital.net, torvalds@...ux-foundation.org, kaber@...sh.net, netdev@...r.kernel.org Subject: Re: Netlink mmap tx security? On 10/15/14 at 07:57pm, David Miller wrote: > From: Daniel Borkmann <dborkman@...hat.com> > Date: Thu, 16 Oct 2014 01:45:22 +0200 > > > On 10/15/2014 04:01 AM, David Miller wrote: > >> From: Andy Lutomirski <luto@...capital.net> > >> Date: Tue, 14 Oct 2014 15:16:46 -0700 > >> > >>> It's at least remotely possible that there's something that assumes > >>> that assumes that the availability of NETLINK_RX_RING implies > >>> NETLINK_TX_RING, which would be unfortunate. > >> > >> I already found one such case, nlmon :-/ > > > > Hmm, can you elaborate? I currently don't think that nlmon cares > > actually. > > nlmon cares, openvswitch cares, etc: > > http://openvswitch.org/pipermail/dev/2013-December/034496.html (Fortunately) the OVS patch has not been merged yet because the number of Netlink sockets created per vport in the current architecture currently make it a non scalable approach. I think introdcing a NETLINK_RX_RING2 and having NETLINK_RX_RING fail is not a bad way out of this. -- 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