<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-stable.git/net/vmw_vsock, branch linux-4.6.y</title>
<subtitle>Linux kernel stable tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/'/>
<entry>
<title>VSOCK: do not disconnect socket when peer has shutdown SEND only</title>
<updated>2016-05-06T03:31:29+00:00</updated>
<author>
<name>Ian Campbell</name>
<email>ian.campbell@docker.com</email>
</author>
<published>2016-05-04T13:21:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=dedc58e067d8c379a15a8a183c5db318201295bb'/>
<id>dedc58e067d8c379a15a8a183c5db318201295bb</id>
<content type='text'>
The peer may be expecting a reply having sent a request and then done a
shutdown(SHUT_WR), so tearing down the whole socket at this point seems
wrong and breaks for me with a client which does a SHUT_WR.

Looking at other socket family's stream_recvmsg callbacks doing a shutdown
here does not seem to be the norm and removing it does not seem to have
had any adverse effects that I can see.

I'm using Stefan's RFC virtio transport patches, I'm unsure of the impact
on the vmci transport.

Signed-off-by: Ian Campbell &lt;ian.campbell@docker.com&gt;
Cc: "David S. Miller" &lt;davem@davemloft.net&gt;
Cc: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Cc: Claudio Imbrenda &lt;imbrenda@linux.vnet.ibm.com&gt;
Cc: Andy King &lt;acking@vmware.com&gt;
Cc: Dmitry Torokhov &lt;dtor@vmware.com&gt;
Cc: Jorgen Hansen &lt;jhansen@vmware.com&gt;
Cc: Adit Ranadive &lt;aditr@vmware.com&gt;
Cc: netdev@vger.kernel.org
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The peer may be expecting a reply having sent a request and then done a
shutdown(SHUT_WR), so tearing down the whole socket at this point seems
wrong and breaks for me with a client which does a SHUT_WR.

Looking at other socket family's stream_recvmsg callbacks doing a shutdown
here does not seem to be the norm and removing it does not seem to have
had any adverse effects that I can see.

I'm using Stefan's RFC virtio transport patches, I'm unsure of the impact
on the vmci transport.

Signed-off-by: Ian Campbell &lt;ian.campbell@docker.com&gt;
Cc: "David S. Miller" &lt;davem@davemloft.net&gt;
Cc: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Cc: Claudio Imbrenda &lt;imbrenda@linux.vnet.ibm.com&gt;
Cc: Andy King &lt;acking@vmware.com&gt;
Cc: Dmitry Torokhov &lt;dtor@vmware.com&gt;
Cc: Jorgen Hansen &lt;jhansen@vmware.com&gt;
Cc: Adit Ranadive &lt;aditr@vmware.com&gt;
Cc: netdev@vger.kernel.org
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>VSOCK: Only check error on skb_recv_datagram when skb is NULL</title>
<updated>2016-04-20T00:42:01+00:00</updated>
<author>
<name>Jorgen Hansen</name>
<email>jhansen@vmware.com</email>
</author>
<published>2016-04-19T06:58:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=9c995cc9a206a008699da82f6cd01e9b2615649a'/>
<id>9c995cc9a206a008699da82f6cd01e9b2615649a</id>
<content type='text'>
If skb_recv_datagram returns an skb, we should ignore the err
value returned. Otherwise, datagram receives will return EAGAIN
when they have to wait for a datagram.

Acked-by: Adit Ranadive &lt;aditr@vmware.com&gt;
Signed-off-by: Jorgen Hansen &lt;jhansen@vmware.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
If skb_recv_datagram returns an skb, we should ignore the err
value returned. Otherwise, datagram receives will return EAGAIN
when they have to wait for a datagram.

Acked-by: Adit Ranadive &lt;aditr@vmware.com&gt;
Signed-off-by: Jorgen Hansen &lt;jhansen@vmware.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>VSOCK: Detach QP check should filter out non matching QPs.</title>
<updated>2016-04-06T20:39:09+00:00</updated>
<author>
<name>Jorgen Hansen</name>
<email>jhansen@vmware.com</email>
</author>
<published>2016-04-05T08:59:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=8ab18d71de8b07d2c4d6f984b718418c09ea45c5'/>
<id>8ab18d71de8b07d2c4d6f984b718418c09ea45c5</id>
<content type='text'>
The check in vmci_transport_peer_detach_cb should only allow a
detach when the qp handle of the transport matches the one in
the detach message.

Testing: Before this change, a detach from a peer on a different
socket would cause an active stream socket to register a detach.

Reviewed-by: George Zhang &lt;georgezhang@vmware.com&gt;
Signed-off-by: Jorgen Hansen &lt;jhansen@vmware.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The check in vmci_transport_peer_detach_cb should only allow a
detach when the qp handle of the transport matches the one in
the detach message.

Testing: Before this change, a detach from a peer on a different
socket would cause an active stream socket to register a detach.

Reviewed-by: George Zhang &lt;georgezhang@vmware.com&gt;
Signed-off-by: Jorgen Hansen &lt;jhansen@vmware.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>AF_VSOCK: Shrink the area influenced by prepare_to_wait</title>
<updated>2016-03-22T20:18:41+00:00</updated>
<author>
<name>Claudio Imbrenda</name>
<email>imbrenda@linux.vnet.ibm.com</email>
</author>
<published>2016-03-22T16:05:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=f7f9b5e7f8eccfd68ffa7b8d74b07c478bb9e7f0'/>
<id>f7f9b5e7f8eccfd68ffa7b8d74b07c478bb9e7f0</id>
<content type='text'>
When a thread is prepared for waiting by calling prepare_to_wait, sleeping
is not allowed until either the wait has taken place or finish_wait has
been called.  The existing code in af_vsock imposed unnecessary no-sleep
assumptions to a broad list of backend functions.
This patch shrinks the influence of prepare_to_wait to the area where it
is strictly needed, therefore relaxing the no-sleep restriction there.

Signed-off-by: Claudio Imbrenda &lt;imbrenda@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When a thread is prepared for waiting by calling prepare_to_wait, sleeping
is not allowed until either the wait has taken place or finish_wait has
been called.  The existing code in af_vsock imposed unnecessary no-sleep
assumptions to a broad list of backend functions.
This patch shrinks the influence of prepare_to_wait to the area where it
is strictly needed, therefore relaxing the no-sleep restriction there.

Signed-off-by: Claudio Imbrenda &lt;imbrenda@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert "vsock: Fix blocking ops call in prepare_to_wait"</title>
<updated>2016-03-22T20:18:41+00:00</updated>
<author>
<name>Claudio Imbrenda</name>
<email>imbrenda@linux.vnet.ibm.com</email>
</author>
<published>2016-03-22T16:05:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=6f57e56a1527d58264ae126eff94fdac067744fc'/>
<id>6f57e56a1527d58264ae126eff94fdac067744fc</id>
<content type='text'>
This reverts commit 5988818008257ca42010d6b43a3e0e48afec9898 ("vsock: Fix
blocking ops call in prepare_to_wait")

The commit reverted with this patch caused us to potentially miss wakeups.
Since the condition is not checked between the prepare_to_wait and the
schedule(), if a wakeup happens after the condition is checked but before
the sleep happens, we will miss it. ( A description of the problem can be
found here: http://www.makelinux.net/ldd3/chp-6-sect-2 ).

By reverting the patch, the behaviour is still incorrect (since we
shouldn't sleep between the prepare_to_wait and the schedule) but at least
it will not miss wakeups.

The next patch in the series actually fixes the behaviour.

Signed-off-by: Claudio Imbrenda &lt;imbrenda@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 5988818008257ca42010d6b43a3e0e48afec9898 ("vsock: Fix
blocking ops call in prepare_to_wait")

The commit reverted with this patch caused us to potentially miss wakeups.
Since the condition is not checked between the prepare_to_wait and the
schedule(), if a wakeup happens after the condition is checked but before
the sleep happens, we will miss it. ( A description of the problem can be
found here: http://www.makelinux.net/ldd3/chp-6-sect-2 ).

By reverting the patch, the behaviour is still incorrect (since we
shouldn't sleep between the prepare_to_wait and the schedule) but at least
it will not miss wakeups.

The next patch in the series actually fixes the behaviour.

Signed-off-by: Claudio Imbrenda &lt;imbrenda@linux.vnet.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>vsock: Fix blocking ops call in prepare_to_wait</title>
<updated>2016-02-13T10:57:39+00:00</updated>
<author>
<name>Laura Abbott</name>
<email>labbott@fedoraproject.org</email>
</author>
<published>2016-02-04T18:50:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=5988818008257ca42010d6b43a3e0e48afec9898'/>
<id>5988818008257ca42010d6b43a3e0e48afec9898</id>
<content type='text'>
We receoved a bug report from someone using vmware:

WARNING: CPU: 3 PID: 660 at kernel/sched/core.c:7389
__might_sleep+0x7d/0x90()
do not call blocking ops when !TASK_RUNNING; state=1 set at
[&lt;ffffffff810fa68d&gt;] prepare_to_wait+0x2d/0x90
Modules linked in: vmw_vsock_vmci_transport vsock snd_seq_midi
snd_seq_midi_event snd_ens1371 iosf_mbi gameport snd_rawmidi
snd_ac97_codec ac97_bus snd_seq coretemp snd_seq_device snd_pcm
snd_timer snd soundcore ppdev crct10dif_pclmul crc32_pclmul
ghash_clmulni_intel vmw_vmci vmw_balloon i2c_piix4 shpchp parport_pc
parport acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace sunrpc btrfs
xor raid6_pq 8021q garp stp llc mrp crc32c_intel serio_raw mptspi vmwgfx
drm_kms_helper ttm drm scsi_transport_spi mptscsih e1000 ata_generic
mptbase pata_acpi
CPU: 3 PID: 660 Comm: vmtoolsd Not tainted
4.2.0-0.rc1.git3.1.fc23.x86_64 #1
Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop
Reference Platform, BIOS 6.00 05/20/2014
 0000000000000000 0000000049e617f3 ffff88006ac37ac8 ffffffff818641f5
 0000000000000000 ffff88006ac37b20 ffff88006ac37b08 ffffffff810ab446
 ffff880068009f40 ffffffff81c63bc0 0000000000000061 0000000000000000
Call Trace:
 [&lt;ffffffff818641f5&gt;] dump_stack+0x4c/0x65
 [&lt;ffffffff810ab446&gt;] warn_slowpath_common+0x86/0xc0
 [&lt;ffffffff810ab4d5&gt;] warn_slowpath_fmt+0x55/0x70
 [&lt;ffffffff8112551d&gt;] ? debug_lockdep_rcu_enabled+0x1d/0x20
 [&lt;ffffffff810fa68d&gt;] ? prepare_to_wait+0x2d/0x90
 [&lt;ffffffff810fa68d&gt;] ? prepare_to_wait+0x2d/0x90
 [&lt;ffffffff810da2bd&gt;] __might_sleep+0x7d/0x90
 [&lt;ffffffff812163b3&gt;] __might_fault+0x43/0xa0
 [&lt;ffffffff81430477&gt;] copy_from_iter+0x87/0x2a0
 [&lt;ffffffffa039460a&gt;] __qp_memcpy_to_queue+0x9a/0x1b0 [vmw_vmci]
 [&lt;ffffffffa0394740&gt;] ? qp_memcpy_to_queue+0x20/0x20 [vmw_vmci]
 [&lt;ffffffffa0394757&gt;] qp_memcpy_to_queue_iov+0x17/0x20 [vmw_vmci]
 [&lt;ffffffffa0394d50&gt;] qp_enqueue_locked+0xa0/0x140 [vmw_vmci]
 [&lt;ffffffffa039593f&gt;] vmci_qpair_enquev+0x4f/0xd0 [vmw_vmci]
 [&lt;ffffffffa04847bb&gt;] vmci_transport_stream_enqueue+0x1b/0x20
[vmw_vsock_vmci_transport]
 [&lt;ffffffffa047ae05&gt;] vsock_stream_sendmsg+0x2c5/0x320 [vsock]
 [&lt;ffffffff810fabd0&gt;] ? wake_atomic_t_function+0x70/0x70
 [&lt;ffffffff81702af8&gt;] sock_sendmsg+0x38/0x50
 [&lt;ffffffff81702ff4&gt;] SYSC_sendto+0x104/0x190
 [&lt;ffffffff8126e25a&gt;] ? vfs_read+0x8a/0x140
 [&lt;ffffffff817042ee&gt;] SyS_sendto+0xe/0x10
 [&lt;ffffffff8186d9ae&gt;] entry_SYSCALL_64_fastpath+0x12/0x76

transport-&gt;stream_enqueue may call copy_to_user so it should
not be called inside a prepare_to_wait. Narrow the scope of
the prepare_to_wait to avoid the bad call. This also applies
to vsock_stream_recvmsg as well.

Reported-by: Vinson Lee &lt;vlee@freedesktop.org&gt;
Tested-by: Vinson Lee &lt;vlee@freedesktop.org&gt;
Signed-off-by: Laura Abbott &lt;labbott@fedoraproject.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We receoved a bug report from someone using vmware:

WARNING: CPU: 3 PID: 660 at kernel/sched/core.c:7389
__might_sleep+0x7d/0x90()
do not call blocking ops when !TASK_RUNNING; state=1 set at
[&lt;ffffffff810fa68d&gt;] prepare_to_wait+0x2d/0x90
Modules linked in: vmw_vsock_vmci_transport vsock snd_seq_midi
snd_seq_midi_event snd_ens1371 iosf_mbi gameport snd_rawmidi
snd_ac97_codec ac97_bus snd_seq coretemp snd_seq_device snd_pcm
snd_timer snd soundcore ppdev crct10dif_pclmul crc32_pclmul
ghash_clmulni_intel vmw_vmci vmw_balloon i2c_piix4 shpchp parport_pc
parport acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace sunrpc btrfs
xor raid6_pq 8021q garp stp llc mrp crc32c_intel serio_raw mptspi vmwgfx
drm_kms_helper ttm drm scsi_transport_spi mptscsih e1000 ata_generic
mptbase pata_acpi
CPU: 3 PID: 660 Comm: vmtoolsd Not tainted
4.2.0-0.rc1.git3.1.fc23.x86_64 #1
Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop
Reference Platform, BIOS 6.00 05/20/2014
 0000000000000000 0000000049e617f3 ffff88006ac37ac8 ffffffff818641f5
 0000000000000000 ffff88006ac37b20 ffff88006ac37b08 ffffffff810ab446
 ffff880068009f40 ffffffff81c63bc0 0000000000000061 0000000000000000
Call Trace:
 [&lt;ffffffff818641f5&gt;] dump_stack+0x4c/0x65
 [&lt;ffffffff810ab446&gt;] warn_slowpath_common+0x86/0xc0
 [&lt;ffffffff810ab4d5&gt;] warn_slowpath_fmt+0x55/0x70
 [&lt;ffffffff8112551d&gt;] ? debug_lockdep_rcu_enabled+0x1d/0x20
 [&lt;ffffffff810fa68d&gt;] ? prepare_to_wait+0x2d/0x90
 [&lt;ffffffff810fa68d&gt;] ? prepare_to_wait+0x2d/0x90
 [&lt;ffffffff810da2bd&gt;] __might_sleep+0x7d/0x90
 [&lt;ffffffff812163b3&gt;] __might_fault+0x43/0xa0
 [&lt;ffffffff81430477&gt;] copy_from_iter+0x87/0x2a0
 [&lt;ffffffffa039460a&gt;] __qp_memcpy_to_queue+0x9a/0x1b0 [vmw_vmci]
 [&lt;ffffffffa0394740&gt;] ? qp_memcpy_to_queue+0x20/0x20 [vmw_vmci]
 [&lt;ffffffffa0394757&gt;] qp_memcpy_to_queue_iov+0x17/0x20 [vmw_vmci]
 [&lt;ffffffffa0394d50&gt;] qp_enqueue_locked+0xa0/0x140 [vmw_vmci]
 [&lt;ffffffffa039593f&gt;] vmci_qpair_enquev+0x4f/0xd0 [vmw_vmci]
 [&lt;ffffffffa04847bb&gt;] vmci_transport_stream_enqueue+0x1b/0x20
[vmw_vsock_vmci_transport]
 [&lt;ffffffffa047ae05&gt;] vsock_stream_sendmsg+0x2c5/0x320 [vsock]
 [&lt;ffffffff810fabd0&gt;] ? wake_atomic_t_function+0x70/0x70
 [&lt;ffffffff81702af8&gt;] sock_sendmsg+0x38/0x50
 [&lt;ffffffff81702ff4&gt;] SYSC_sendto+0x104/0x190
 [&lt;ffffffff8126e25a&gt;] ? vfs_read+0x8a/0x140
 [&lt;ffffffff817042ee&gt;] SyS_sendto+0xe/0x10
 [&lt;ffffffff8186d9ae&gt;] entry_SYSCALL_64_fastpath+0x12/0x76

transport-&gt;stream_enqueue may call copy_to_user so it should
not be called inside a prepare_to_wait. Narrow the scope of
the prepare_to_wait to avoid the bad call. This also applies
to vsock_stream_recvmsg as well.

Reported-by: Vinson Lee &lt;vlee@freedesktop.org&gt;
Tested-by: Vinson Lee &lt;vlee@freedesktop.org&gt;
Signed-off-by: Laura Abbott &lt;labbott@fedoraproject.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert "Merge branch 'vsock-virtio'"</title>
<updated>2015-12-09T02:55:49+00:00</updated>
<author>
<name>Stefan Hajnoczi</name>
<email>stefanha@redhat.com</email>
</author>
<published>2015-12-09T02:51:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=8ac2837c89c8c0fcad557e4380aeef80580390f9'/>
<id>8ac2837c89c8c0fcad557e4380aeef80580390f9</id>
<content type='text'>
This reverts commit 0d76d6e8b2507983a2cae4c09880798079007421 and merge
commit c402293bd76fbc93e52ef8c0947ab81eea3ae019, reversing changes made
to c89359a42e2a49656451569c382eed63e781153c.

The virtio-vsock device specification is not finalized yet.  Michael
Tsirkin voiced concerned about merging this code when the hardware
interface (and possibly the userspace interface) could still change.

Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 0d76d6e8b2507983a2cae4c09880798079007421 and merge
commit c402293bd76fbc93e52ef8c0947ab81eea3ae019, reversing changes made
to c89359a42e2a49656451569c382eed63e781153c.

The virtio-vsock device specification is not finalized yet.  Michael
Tsirkin voiced concerned about merging this code when the hardware
interface (and possibly the userspace interface) could still change.

Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>VSOCK: Add Makefile and Kconfig</title>
<updated>2015-12-03T20:05:55+00:00</updated>
<author>
<name>Asias He</name>
<email>asias@redhat.com</email>
</author>
<published>2015-12-02T06:44:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=8a2a2029893b4c35d1aba2932111a1a164b9c948'/>
<id>8a2a2029893b4c35d1aba2932111a1a164b9c948</id>
<content type='text'>
Enable virtio-vsock and vhost-vsock.

Signed-off-by: Asias He &lt;asias@redhat.com&gt;
Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Enable virtio-vsock and vhost-vsock.

Signed-off-by: Asias He &lt;asias@redhat.com&gt;
Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>VSOCK: Introduce virtio-vsock.ko</title>
<updated>2015-12-03T20:05:55+00:00</updated>
<author>
<name>Asias He</name>
<email>asias@redhat.com</email>
</author>
<published>2015-12-02T06:44:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=32e61b06b6946ba137723c5b1de2a1fdb2e0e0a5'/>
<id>32e61b06b6946ba137723c5b1de2a1fdb2e0e0a5</id>
<content type='text'>
VM sockets virtio transport implementation. This module runs in guest
kernel.

Signed-off-by: Asias He &lt;asias@redhat.com&gt;
Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
VM sockets virtio transport implementation. This module runs in guest
kernel.

Signed-off-by: Asias He &lt;asias@redhat.com&gt;
Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>VSOCK: Introduce virtio-vsock-common.ko</title>
<updated>2015-12-03T20:05:55+00:00</updated>
<author>
<name>Asias He</name>
<email>asias@redhat.com</email>
</author>
<published>2015-12-02T06:44:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=80a19e338d458abb5a700df3fd00795c51361f06'/>
<id>80a19e338d458abb5a700df3fd00795c51361f06</id>
<content type='text'>
This module contains the common code and header files for the following
virtio-vsock and virtio-vhost kernel modules.

Signed-off-by: Asias He &lt;asias@redhat.com&gt;
Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This module contains the common code and header files for the following
virtio-vsock and virtio-vhost kernel modules.

Signed-off-by: Asias He &lt;asias@redhat.com&gt;
Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</pre>
</div>
</content>
</entry>
</feed>
