Jan Beulich 089bc0143f xen-blkback: don't leak stack data via response ring ... 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. Cc: stable@vger.kernel.org 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>		2017-06-13 16:28:32 -04:00
..
blkback.c	xen-blkback: don't leak stack data via response ring	2017-06-13 16:28:32 -04:00
common.h	xen-blkback: don't leak stack data via response ring	2017-06-13 16:28:32 -04:00
Makefile	xen/blkback: Squash vbd.c,interface.c in blkback.c and xenbus.c respectivly.	2011-04-20 11:57:59 -04:00
xenbus.c	xen/blkback: don't use xen_blkif_get() in xen-blkback kthread	2017-06-13 16:27:39 -04:00