net: ena: fix rare bug when failed restart/resume is followed by driver removal
In a rare scenario when ena_device_restore() fails, followed by device
remove, an FLR will not be issued. In this case, the device will keep
sending asynchronous AENQ keep-alive events, even after driver removal,
leading to memory corruption.
Fixes: 8c5c7abdeb ("net: ena: add power management ops to the ENA driver")
Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
			
			
This commit is contained in:
		
							parent
							
								
									d79c3888bd
								
							
						
					
					
						commit
						d7703ddbd7
					
				| @ -2619,7 +2619,11 @@ err_disable_msix: | ||||
| 	ena_free_mgmnt_irq(adapter); | ||||
| 	ena_disable_msix(adapter); | ||||
| err_device_destroy: | ||||
| 	ena_com_abort_admin_commands(ena_dev); | ||||
| 	ena_com_wait_for_abort_completion(ena_dev); | ||||
| 	ena_com_admin_destroy(ena_dev); | ||||
| 	ena_com_mmio_reg_read_request_destroy(ena_dev); | ||||
| 	ena_com_dev_reset(ena_dev, ENA_REGS_RESET_DRIVER_INVALID_STATE); | ||||
| err: | ||||
| 	clear_bit(ENA_FLAG_DEVICE_RUNNING, &adapter->flags); | ||||
| 	clear_bit(ENA_FLAG_ONGOING_RESET, &adapter->flags); | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user