locking/mutex: Introduce devm_mutex_init()
Using of devm API leads to a certain order of releasing resources. So all dependent resources which are not devm-wrapped should be deleted with respect to devm-release order. Mutex is one of such objects that often is bound to other resources and has no own devm wrapping. Since mutex_destroy() actually does nothing in non-debug builds frequently calling mutex_destroy() is just ignored which is safe for now but wrong formally and can lead to a problem if mutex_destroy() will be extended so introduce devm_mutex_init(). Suggested-by:Christophe Leroy <christophe.leroy@csgroup.eu> Signed-off-by:
George Stark <gnstark@salutedevices.com> Reviewed-by:
Christophe Leroy <christophe.leroy@csgroup.eu> Reviewed-by:
Andy Shevchenko <andy.shevchenko@gmail.com> Reviewed-by:
Marek Behún <kabel@kernel.org> Acked-by:
Waiman Long <longman@redhat.com> Link: https://lore.kernel.org/r/20240411161032.609544-2-gnstark@salutedevices.comSigned-off-by:
Lee Jones <lee@kernel.org>
Showing
Please register or sign in to comment