Jan Beulich 11e8e55be1 xen-blkback: don't leak stack data via response ring ... commit 089bc0143f489bd3a4578bdff5f4ca68fb26f341 upstream. Rather than constructing a local structure instance on the stack, fill the fields directly on the shared ring, just like other backends do. Build on the fact that all response structure flavors are actually identical (the old code did make this assumption too). This is XSA-216. Signed-off-by: Jan Beulich <jbeulich@suse.com> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> [bwh: Backported to 4.4: adjust context] Signed-off-by: Ben Hutchings <ben.hutchings@codethink.co.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2017-11-21 09:21:17 +01:00
..
blkback.c	xen-blkback: don't leak stack data via response ring	2017-11-21 09:21:17 +01:00
common.h	xen-blkback: don't leak stack data via response ring	2017-11-21 09:21:17 +01:00
Makefile
xenbus.c	xen/blkback: don't use xen_blkif_get() in xen-blkback kthread	2017-08-06 19:19:43 -07:00