xenbus: don't free other end details too early
authorJan Beulich <JBeulich@suse.com>
Mon, 5 Mar 2012 17:11:31 +0000 (17:11 +0000)
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Tue, 13 Mar 2012 18:15:29 +0000 (14:15 -0400)
commitbd0d5aa417d40d6b996fb7b5c926bcecd56c8984
tree7e05120b899c9bcabe1422d0c582c49d97cd1037
parent73c154c60be106b47f15d1111fc2d75cc7a436f2
xenbus: don't free other end details too early

The individual drivers' remove functions could legitimately attempt to
access this information (for logging messages if nothing else). Note
that I did not in fact observe a problem anywhere, but I came across
this while looking into the reasons for what turned out to need the
fix at https://lkml.org/lkml/2012/3/5/336 to vsprintf().

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
drivers/xen/xenbus/xenbus_probe.c