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.