search for: exaplain

...r allowed half-closed socket on the host side. > > > > As Jorgen explained [1] this is due to the implementation of VMCI. > > > > Since we want to have the same behaviour across all transports, this > > series adds a section in the "Implementation notes" to exaplain this > > behaviour, and changes the vhost_transport to behave the same way. > > > > [1] https://patchwork.ozlabs.org/cover/847998/#1831400 > > Half closed sockets are very useful, and lots of > applications use tricks to swap a vsock for a tcp socket, > which might a...

...r allowed half-closed socket on the host side. > > > > As Jorgen explained [1] this is due to the implementation of VMCI. > > > > Since we want to have the same behaviour across all transports, this > > series adds a section in the "Implementation notes" to exaplain this > > behaviour, and changes the vhost_transport to behave the same way. > > > > [1] https://patchwork.ozlabs.org/cover/847998/#1831400 > > Half closed sockets are very useful, and lots of > applications use tricks to swap a vsock for a tcp socket, > which might a...

...sockets and we discovered that vmci_transport never allowed half-closed socket on the host side. As Jorgen explained [1] this is due to the implementation of VMCI. Since we want to have the same behaviour across all transports, this series adds a section in the "Implementation notes" to exaplain this behaviour, and changes the vhost_transport to behave the same way. [1] https://patchwork.ozlabs.org/cover/847998/#1831400 Stefano Garzarella (2): vsock: add half-closed socket details in the implementation notes vhost/vsock: don't allow half-closed socket in the host drivers/vhost/...

...sockets and we discovered that vmci_transport never allowed half-closed socket on the host side. As Jorgen explained [1] this is due to the implementation of VMCI. Since we want to have the same behaviour across all transports, this series adds a section in the "Implementation notes" to exaplain this behaviour, and changes the vhost_transport to behave the same way. [1] https://patchwork.ozlabs.org/cover/847998/#1831400 Stefano Garzarella (2): vsock: add half-closed socket details in the implementation notes vhost/vsock: don't allow half-closed socket in the host drivers/vhost/...

...that vmci_transport never allowed half-closed socket on the host side. > > As Jorgen explained [1] this is due to the implementation of VMCI. > > Since we want to have the same behaviour across all transports, this > series adds a section in the "Implementation notes" to exaplain this > behaviour, and changes the vhost_transport to behave the same way. > > [1] https://patchwork.ozlabs.org/cover/847998/#1831400 Half closed sockets are very useful, and lots of applications use tricks to swap a vsock for a tcp socket, which might as a result break. If VMCI really c...

...ket on the host side. > > > > > > As Jorgen explained [1] this is due to the implementation of VMCI. > > > > > > Since we want to have the same behaviour across all transports, this > > > series adds a section in the "Implementation notes" to exaplain this > > > behaviour, and changes the vhost_transport to behave the same way. > > > > > > [1] https://patchwork.ozlabs.org/cover/847998/#1831400 > > > > Half closed sockets are very useful, and lots of > > applications use tricks to swap a vsock for a...

Whenever I insert a symbol in Word 2007, it crashes. It doesn't crash in PowerPoint 2007 or Excel 2007. This is because a dialog box comes up instead whilst in Word, it is more of a drop down menu. This is my counsel output: Code: wine winword.exe fixme:heap:HeapSetInformation 0x110000 1 (nil) 0 fixme:heap:HeapSetInformation 0x110000 1 (nil) 0 fixme:heap:HeapSetInformation 0x110000 1 (nil)