Re: [PATCH] VSOCK: Don't call vsock_stream_has_data in atomic context

2017-11-23 Thread David Miller
From: Jorgen Hansen Date: Tue, 21 Nov 2017 02:46:24 -0800 > When using the host personality, VMCI will grab a mutex for any > queue pair access. In the detach callback for the vmci vsock > transport, we call vsock_stream_has_data while holding a spinlock, > and vsock_stream_has_data will access a

Re: [PATCH] VSOCK: Don't call vsock_stream_has_data in atomic context

2017-11-23 Thread Stefan Hajnoczi
On Tue, Nov 21, 2017 at 10:46 AM, Jorgen Hansen wrote: > When using the host personality, VMCI will grab a mutex for any > queue pair access. In the detach callback for the vmci vsock > transport, we call vsock_stream_has_data while holding a spinlock, > and vsock_stream_has_data will access a que

[PATCH] VSOCK: Don't call vsock_stream_has_data in atomic context

2017-11-21 Thread Jorgen Hansen
When using the host personality, VMCI will grab a mutex for any queue pair access. In the detach callback for the vmci vsock transport, we call vsock_stream_has_data while holding a spinlock, and vsock_stream_has_data will access a queue pair. To avoid this, we can simply omit calling vsock_stream