netdev - RE: [ovs-dev] [GIT PULL v2] Open vSwitch

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: <0199E0D51A61344794750DC57738F58E7586A7435D@GVW1118EXC.americas.hpqcorp.net>
Date:	Mon, 28 Nov 2011 18:52:31 +0000
From:	"Fischer, Anna" <anna.fischer@...com>
To:	Ben Pfaff <blp@...ira.com>
CC:	Herbert Xu <herbert@...dor.apana.org.au>,
	"jhs@...atatu.com" <jhs@...atatu.com>,
	"dev@...nvswitch.org" <dev@...nvswitch.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>
Subject: RE: [ovs-dev] [GIT PULL v2] Open vSwitch

> Subject: Re: [ovs-dev] [GIT PULL v2] Open vSwitch
> 
> On Mon, Nov 28, 2011 at 01:54:16PM +0000, Fischer, Anna wrote:
> > Yes, I mentioned this months ago, and I am surprised this critical
> > issue has never been picked up on and addressed. With a flaw like
> this
> > there is no chance this component can be used in any serious
> > virtualization deployment where different customers share the same
> > physical server.
> 
> It was addressed, by introducing additional queues and using them in
> userspace.
> 
> This is documented in NEWS:
> 
>     - Flow setups are now processed in a round-robin manner across
> ports
>       to prevent any single client from monopolizing the CPU and
> conducting
>       a denial of service attack.

OK, that addresses my point, thanks. Ideally there should be smarter or more flexible algorithms than just a round robin scheduler, but it is a start.

Anna
--
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