Skip to main content

Browse the archive

Revision 42b5212fee4f57907e9415b18fe19c13e65574bc authored by David Vrabel on 02 February 2015, 16:57:51 UTC, committed by David S. Miller on 03 February 2015, 03:39:04 UTC 
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>
1 parent 5a2e87b
Raw File
Makefile 
LATEXFILE = cdrom-standard

all:
	make clean
	latex $(LATEXFILE)
	latex $(LATEXFILE)
	@if [ -x `which gv` ]; then \
		`dvips -q -t letter -o $(LATEXFILE).ps $(LATEXFILE).dvi` ;\
		`gv -antialias -media letter -nocenter $(LATEXFILE).ps` ;\
	else \
		`xdvi $(LATEXFILE).dvi &` ;\
	fi
	make sortofclean

clean:
	rm -f $(LATEXFILE).ps $(LATEXFILE).dvi $(LATEXFILE).aux $(LATEXFILE).log 

sortofclean:
	rm -f $(LATEXFILE).aux $(LATEXFILE).log
back to top