[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250204-must_check-devm_mutex_init-v2-0-7b6271c4b7e6@weissschuh.net>
Date: Tue, 04 Feb 2025 07:52:49 +0100
From: Thomas Weißschuh <linux@...ssschuh.net>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Will Deacon <will@...nel.org>, Waiman Long <longman@...hat.com>,
Boqun Feng <boqun.feng@...il.com>, Pavel Machek <pavel@....cz>,
Lee Jones <lee@...nel.org>,
Vicentiu Galanopulo <vicentiu.galanopulo@...ote-tech.co.uk>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-leds@...r.kernel.org,
Thomas Weißschuh <linux@...ssschuh.net>
Subject: [PATCH v2 0/2] locking/mutex: Mark devm_mutex_init() as
__must_check
Even if it's not critical, the avoidance of checking the error code
from devm_mutex_init() call today diminishes the point of using devm
variant of it. Tomorrow it may even leak something. Enforce all callers
checking the return value through the compiler.
The series should go through the locking tree.
Signed-off-by: Thomas Weißschuh <linux@...ssschuh.net>
---
Changes in v2:
- Rebase on 6.14-rc1
- Fix up leds-1202 driver
- Link to v1: https://lore.kernel.org/r/20241202-must_check-devm_mutex_init-v1-1-e60eb97b8c72@weissschuh.net
---
Thomas Weißschuh (2):
leds: st1202: Check for error code from devm_mutex_init() call
locking/mutex: Mark devm_mutex_init() as __must_check
drivers/leds/leds-st1202.c | 4 +++-
include/linux/mutex.h | 17 ++++++++---------
2 files changed, 11 insertions(+), 10 deletions(-)
---
base-commit: 2014c95afecee3e76ca4a56956a936e23283f05b
change-id: 20241031-must_check-devm_mutex_init-cac583bda8fe
Best regards,
--
Thomas Weißschuh <linux@...ssschuh.net>
Powered by blists - more mailing lists