d3bf5efc1f
When detaching device trees parent devices must be detached prior to detaching its children. This is because parent devices can have pointers to the child devices in their softcs which are not invalidated by device_delete_child(). This can cause use after free issues and panic(). Device drivers implementing trees, must ensure its detach function detaches or deletes all its children before returning. While at it remove now redundant device_detach() calls before device_delete_child() and device_delete_children(), mostly in the USB controller drivers. Tested by: Jan Henrik Sylvester <me@janh.de> Reviewed by: jhb Differential Revision: https://reviews.freebsd.org/D8070 MFC after: 2 weeks |
||
|---|---|---|
| .. | ||
| chrome_ec_spi.c | ||
| chrome_ec.c | ||
| chrome_ec.h | ||
| chrome_kb.c | ||
| chrome_kb.h | ||
| exynos5_combiner.c | ||
| exynos5_combiner.h | ||
| exynos5_common.c | ||
| exynos5_common.h | ||
| exynos5_ehci.c | ||
| exynos5_fimd.c | ||
| exynos5_i2c.c | ||
| exynos5_machdep.c | ||
| exynos5_mct.c | ||
| exynos5_mp.c | ||
| exynos5_pad.c | ||
| exynos5_pad.h | ||
| exynos5_pmu.c | ||
| exynos5_pmu.h | ||
| exynos5_spi.c | ||
| exynos5_usb_phy.c | ||
| exynos5_xhci.c | ||
| exynos_uart.c | ||
| exynos_uart.h | ||
| files.exynos5 | ||
| std.exynos5250 | ||
| std.exynos5420 | ||