Re: [PATCH v2] xen/netback: Wake dealloc thread after completing zerocopy work

2015-08-06 Thread David Miller
From: Ross Lagerwall Date: Tue, 4 Aug 2015 15:40:59 +0100 > Waking the dealloc thread before decrementing inflight_packets is racy > because it means the thread may go to sleep before inflight_packets is > decremented. If kthread_stop() has already been called, the dealloc > thread may wait forev

[PATCH v2] xen/netback: Wake dealloc thread after completing zerocopy work

2015-08-04 Thread Ross Lagerwall
Waking the dealloc thread before decrementing inflight_packets is racy because it means the thread may go to sleep before inflight_packets is decremented. If kthread_stop() has already been called, the dealloc thread may wait forever with nothing to wake it. Instead, wake the thread only after decr

Re: [PATCH v2] xen/netback: Wake dealloc thread after completing zerocopy work

2015-08-04 Thread Wei Liu
On Tue, Aug 04, 2015 at 03:40:59PM +0100, Ross Lagerwall wrote: > Waking the dealloc thread before decrementing inflight_packets is racy > because it means the thread may go to sleep before inflight_packets is > decremented. If kthread_stop() has already been called, the dealloc > thread may wait f