Hello! On 11/16/20 11:23 AM, Lukas Wunner wrote: > rpcif_spi_remove() accesses the driver's private data after calling > spi_unregister_controller() even though that function releases the last > reference on the spi_controller and thereby frees the private data. OK, your analysis seems correct (sorry for the delay admitting this :-). Not sure why spi_unregister_controller() drops the device reference while spi_register_controller() itself doesn't allocate the memory... > Fix by switching over to the new devm_spi_alloc_master() helper which > keeps the private data accessible until the driver has unbound. Perhaps the order of the calls in the remove() method could be reversed? > Fixes: eb8d6d464a27 ("spi: add Renesas RPC-IF driver") > Signed-off-by: Lukas Wunner <lukas@xxxxxxxxx> > Cc: <stable@xxxxxxxxxxxxxxx> # v5.9+: 5e844cc37a5c: spi: Introduce device-managed SPI controller allocation > Cc: <stable@xxxxxxxxxxxxxxx> # v5.9+ > Cc: Sergei Shtylyov <sergei.shtylyov@xxxxxxxxxxxxxxxxxx> [...] MBR, Sergei