Juergen Gross 560e64413b xen/console: harden hvc_xen against event channel storms ... commit fe415186b4 upstream. The Xen console driver is still vulnerable for an attack via excessive number of events sent by the backend. Fix that by using a lateeoi event channel. For the normal domU initial console this requires the introduction of bind_evtchn_to_irq_lateeoi() as there is no xenbus device available at the time the event channel is bound to the irq. As the decision whether an interrupt was spurious or not requires to test for bytes having been read from the backend, move sending the event into the if statement, as sending an event without having found any bytes to be read is making no sense at all. This is part of XSA-391 Signed-off-by: Juergen Gross <jgross@suse.com> Reviewed-by: Jan Beulich <jbeulich@suse.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2021-12-22 09:29:40 +01:00
..
hvc_console.c	Revert "tty: hvc: Fix data abort due to race in hvc_open"	2020-06-30 15:37:13 -04:00
hvc_console.h
hvc_dcc.c
hvc_irq.c
hvc_iucv.c
hvc_opal.c
hvc_riscv_sbi.c
hvc_rtas.c
hvc_udbg.c
hvc_vio.c
hvc_xen.c	xen/console: harden hvc_xen against event channel storms	2021-12-22 09:29:40 +01:00
hvcs.c	tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()	2020-10-29 09:57:38 +01:00
hvsi.c	hvsi: don't panic on tty_register_driver failure	2021-09-22 12:26:30 +02:00
hvsi_lib.c
Kconfig
Makefile