In case there are still devices in the hashmap when the module is
unloaded, we need to free the hashmap before the devices, because
the hashmap key points to the device's name instead of making a copy.
Reported-by: Alexander Patrakov
Signed-off-by: David Henningsson
---
I haven't reproduced it
03.12.2014 16:37, David Henningsson wrote:
In case there are still devices in the hashmap when the module is
unloaded, we need to free the hashmap before the devices, because
the hashmap key points to the device's name instead of making a copy.
Reported-by: Alexander Patrakov
Signed-off-by: Dav
03.12.2014 16:55, Alexander E. Patrakov wrote:
03.12.2014 16:37, David Henningsson wrote:
In case there are still devices in the hashmap when the module is
unloaded, we need to free the hashmap before the devices, because
the hashmap key points to the device's name instead of making a copy.
Rep
03.12.2014 16:37, David Henningsson wrote:
In case there are still devices in the hashmap when the module is
unloaded, we need to free the hashmap before the devices, because
the hashmap key points to the device's name instead of making a copy.
Reported-by: Alexander Patrakov
Signed-off-by: Dav
On Wed, 2014-12-03 at 12:37 +0100, David Henningsson wrote:
> In case there are still devices in the hashmap when the module is
> unloaded, we need to free the hashmap before the devices, because
> the hashmap key points to the device's name instead of making a copy.
>
> Reported-by: Alexander Pat
