From: Michael S. Tsirkin m...@redhat.com
Date: Wed, 5 Jun 2013 12:02:52 +0300
On Wed, Jun 05, 2013 at 03:40:46PM +0800, Jason Wang wrote:
When we decide not use zero-copy, msg.control should be set to NULL otherwise
macvtap/tap may set zerocopy callbacks which may decrease the kref of ubufs
Hello.
On 06/06/2013 07:27 AM, Jason Wang wrote:
When we decide not use zero-copy, msg.control should be set to NULL
otherwise
macvtap/tap may set zerocopy callbacks which may decrease the kref of
ubufs
wrongly.
Bug were introduced by commit cedb9bdce099206290a2bdd02ce47a7b253b6a84
(vhost-net:
When we decide not use zero-copy, msg.control should be set to NULL otherwise
macvtap/tap may set zerocopy callbacks which may decrease the kref of ubufs
wrongly.
Bug were introduced by commit cedb9bdce099206290a2bdd02ce47a7b253b6a84
(vhost-net: skip head management if no outstanding).
This
On Wed, Jun 05, 2013 at 03:40:46PM +0800, Jason Wang wrote:
When we decide not use zero-copy, msg.control should be set to NULL otherwise
macvtap/tap may set zerocopy callbacks which may decrease the kref of ubufs
wrongly.
Bug were introduced by commit
Hello.
On 05-06-2013 11:40, Jason Wang wrote:
When we decide not use zero-copy, msg.control should be set to NULL otherwise
macvtap/tap may set zerocopy callbacks which may decrease the kref of ubufs
wrongly.
Bug were introduced by commit cedb9bdce099206290a2bdd02ce47a7b253b6a84
(vhost-net:
On 06/05/2013 09:44 PM, Sergei Shtylyov wrote:
Hello.
On 05-06-2013 11:40, Jason Wang wrote:
When we decide not use zero-copy, msg.control should be set to NULL
otherwise
macvtap/tap may set zerocopy callbacks which may decrease the kref of
ubufs
wrongly.
Bug were introduced by commit