summaryrefslogtreecommitdiff
path: root/net
diff options
context:
space:
mode:
authorDavid Vrabel <david.vrabel@citrix.com>2015-02-02 16:57:51 +0000
committerDavid S. Miller <davem@davemloft.net>2015-02-02 19:39:04 -0800
commit42b5212fee4f57907e9415b18fe19c13e65574bc (patch)
tree3fb44adcfd6de16f9e3ceddcf46d7a2c9c54532c /net
parent5a2e87b16875f9b83b7e9494cf1fce8e17dc764a (diff)
xen-netback: stop the guest rx thread after a fatal error
After commit e9d8b2c2968499c1f96563e6522c56958d5a1d0d (xen-netback: disable rogue vif in kthread context), a fatal (protocol) error would leave the guest Rx thread spinning, wasting CPU time. Commit ecf08d2dbb96d5a4b4bcc53a39e8d29cc8fef02e (xen-netback: reintroduce guest Rx stall detection) made this even worse by removing a cond_resched() from this path. Since a fatal error is non-recoverable, just allow the guest Rx thread to exit. This requires taking additional refs to the task so the thread exiting early is handled safely. Signed-off-by: David Vrabel <david.vrabel@citrix.com> Reported-by: Julien Grall <julien.grall@linaro.org> Tested-by: Julien Grall <julien.grall@linaro.org> Acked-by: Wei Liu <wei.liu2@citrix.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions