On Mon, Sep 21, 2020 at 01:08:05PM +0200, Sascha Hauer wrote: > I see the following KASan use-after-free messages from the fsl-dspi > driver. It seems that after spi_unregister_controller() has been called > no references to the SPI controller device are left and the device is > freed in spi_controller_release(). This also frees the driver data > structure which is allocated with spi_alloc_master(). Nevertheless all > users of spi_unregister_controller() still use their driver data after > having called spi_unregister_controller(). > Any idea what to do about this? Drivers that need to use their driver_data in remove() should either use devm_spi_register_controller() or not use spi_register_controller() to allocate driver_data. Depending on what the remove function does it may not be practical to do the former, most likely it won't be.
Attachment:
signature.asc
Description: PGP signature
