[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <176962987100.2495410.7579653018712943913.tip-bot2@tip-bot2>
Date: Wed, 28 Jan 2026 19:51:11 -0000
From: "tip-bot2 for Marco Elver" <tip-bot2@...utronix.de>
To: linux-tip-commits@...r.kernel.org
Cc: Marco Elver <elver@...gle.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: [tip: locking/core] tomoyo: Use scoped init guard
The following commit has been merged into the locking/core branch of tip:
Commit-ID: 41539433b32d71aea9f7ada84dc6a8bd014ca50d
Gitweb: https://git.kernel.org/tip/41539433b32d71aea9f7ada84dc6a8bd014ca50d
Author: Marco Elver <elver@...gle.com>
AuthorDate: Mon, 19 Jan 2026 10:05:55 +01:00
Committer: Peter Zijlstra <peterz@...radead.org>
CommitterDate: Wed, 28 Jan 2026 20:45:25 +01:00
tomoyo: Use scoped init guard
Convert lock initialization to scoped guarded initialization where
lock-guarded members are initialized in the same scope.
This ensures the context analysis treats the context as active during member
initialization. This is required to avoid errors once implicit context
assertion is removed.
Signed-off-by: Marco Elver <elver@...gle.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
Link: https://patch.msgid.link/20260119094029.1344361-6-elver@google.com
---
security/tomoyo/common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/tomoyo/common.c b/security/tomoyo/common.c
index 86ce56c..7e1f825 100644
--- a/security/tomoyo/common.c
+++ b/security/tomoyo/common.c
@@ -2557,7 +2557,7 @@ int tomoyo_open_control(const u8 type, struct file *file)
if (!head)
return -ENOMEM;
- mutex_init(&head->io_sem);
+ guard(mutex_init)(&head->io_sem);
head->type = type;
switch (type) {
case TOMOYO_DOMAINPOLICY:
Powered by blists - more mailing lists