From: "Mickaël Salaün" <mic@digikod.net>
To: "Günther Noack" <gnoack@google.com>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Konstantin Meskhidze" <konstantin.meskhidze@huawei.com>,
"Matthieu Buffet" <matthieu@buffet.re>,
"Mikhail Ivanov" <ivanov.mikhail1@huawei-partners.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Shervin Oloumi" <enlightened@chromium.org>,
"Waiman Long" <longman@redhat.com>,
"Will Deacon" <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [PATCH v1 0/4] Use scoped guards on Landlock
Date: Mon, 13 Jan 2025 17:11:08 +0100 [thread overview]
Message-ID: <20250113161112.452505-1-mic@digikod.net> (raw)
Using scoped guards helps simplifying error handling by removing goto
statements.
Only one macro was missing for mutex_lock() calls with
SINGLE_DEPTH_NESTING.
Regards,
Mickaël Salaün (4):
landlock: Use scoped guards for ruleset
landlock: Use scoped guards for ruleset in landlock_add_rule()
locking/mutex: Add mutex_nest_1() scoped guard
landlock: Use scoped guards for mutex
include/linux/mutex.h | 2 +
security/landlock/ruleset.c | 74 +++++++++++++++---------------------
security/landlock/ruleset.h | 5 +++
security/landlock/syscalls.c | 39 ++++++-------------
4 files changed, 50 insertions(+), 70 deletions(-)
base-commit: 9d89551994a430b50c4fffcb1e617a057fa76e20
--
2.47.1
next reply other threads:[~2025-01-13 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 16:11 Mickaël Salaün [this message]
2025-01-13 16:11 ` [PATCH v1 1/4] landlock: Use scoped guards for ruleset Mickaël Salaün
2025-01-13 22:05 ` Günther Noack
2025-01-13 16:11 ` [PATCH v1 2/4] landlock: Use scoped guards for ruleset in landlock_add_rule() Mickaël Salaün
2025-01-13 22:06 ` Günther Noack
2025-01-13 16:11 ` [PATCH v1 3/4] locking/mutex: Add mutex_nest_1() scoped guard Mickaël Salaün
2025-01-13 16:11 ` [PATCH v1 4/4] landlock: Use scoped guards for mutex Mickaël Salaün
2025-01-14 9:25 ` Günther Noack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250113161112.452505-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=boqun.feng@gmail.com \
--cc=enlightened@chromium.org \
--cc=gnoack@google.com \
--cc=ivanov.mikhail1@huawei-partners.com \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=longman@redhat.com \
--cc=matthieu@buffet.re \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®