Il 02/06/2014 23:58, Eric Dumazet ha scritto:
This looks dubious

What about using kfree_rcu() instead ?

It would lead to unbound allocation from userspace.

translate_desc() still uses rcu_read_lock(), its not clear if the mutex
is really held.

Yes, vhost_get_vq_desc must be called with the vq mutex held.

The rcu_read_lock/unlock in translate_desc is unnecessary.

Paolo
_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

Reply via email to