diff options
| author | Doug Goldstein | 2015-11-26 21:32:39 +0100 |
|---|---|---|
| committer | Konrad Rzeszutek Wilk | 2015-12-18 17:38:48 +0100 |
| commit | 584a561a6fee0d258f9ca644f58b73d9a41b8a46 (patch) | |
| tree | d4882559fa179adcfb71ffebf0e2158fabb6cbd1 /drivers/xen/xen-scsiback.c | |
| parent | xen/pciback: Don't allow MSI-X ops if PCI_COMMAND_MEMORY is not set. (diff) | |
| download | kernel-qcow2-linux-584a561a6fee0d258f9ca644f58b73d9a41b8a46.tar.gz kernel-qcow2-linux-584a561a6fee0d258f9ca644f58b73d9a41b8a46.tar.xz kernel-qcow2-linux-584a561a6fee0d258f9ca644f58b73d9a41b8a46.zip | |
xen-pciback: fix up cleanup path when alloc fails
When allocating a pciback device fails, clear the private
field. This could lead to an use-after free, however
the 'really_probe' takes care of setting
dev_set_drvdata(dev, NULL) in its failure path (which we would
exercise if the ->probe function failed), so we we
are OK. However lets be defensive as the code can change.
Going forward we should clean up the pci_set_drvdata(dev, NULL)
in the various code-base. That will be for another day.
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Reported-by: Jonathan Creekmore <jonathan.creekmore@gmail.com>
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'drivers/xen/xen-scsiback.c')
0 files changed, 0 insertions, 0 deletions