On 17/06/2015 15:13, Michael S. Tsirkin wrote: > > > Considering userspace can be malicious, I guess yes. > > I don't think it's a valid concern in this case, > > setting limit back from 509 to 64 will not help here in any way, > > userspace still can create as many vhost instances as it needs > > to consume memory it desires. > > Not really since vhost char device isn't world-accessible. > It's typically opened by a priveledged tool, the fd is > then passed to an unpriveledged userspace, or permissions dropped. Then what's the concern anyway? Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
