diff options
author | Thomas Weißschuh <linux@weissschuh.net> | 2025-06-17 19:08:14 +0200 |
---|---|---|
committer | Boqun Feng <boqun.feng@gmail.com> | 2025-07-11 15:11:54 -0700 |
commit | daec29dcc8731b7596690ab9f647839e4584a86d (patch) | |
tree | 1af9d7f03fe3024ad096621ecaa5d545c6f16835 /scripts/gdb/linux/xarray.py | |
parent | 3b07bb900af7f43f13f9ff398b4c6ca1dee217cd (diff) |
locking/mutex: Mark devm_mutex_init() as __must_check
devm_mutex_init() can fail. With CONFIG_DEBUG_MUTEXES=y the mutex will be
marked as unusable and trigger errors on usage.
Enforce all callers check the return value through the compiler.
As devm_mutex_init() itself is a macro, it can not be annotated
directly. Annotate __devm_mutex_init() instead.
Unfortunately __must_check/warn_unused_result don't propagate through
statement expression. So move the statement expression into the argument
list of the call to __devm_mutex_init() through a helper macro.
Suggested-by: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
Link: https://lore.kernel.org/r/20250617-must_check-devm_mutex_init-v7-3-d9e449f4d224@weissschuh.net
Diffstat (limited to 'scripts/gdb/linux/xarray.py')
0 files changed, 0 insertions, 0 deletions