From: Paul Moore <paul@paul-moore.com>
To: selinux@vger.kernel.org
Subject: Re: [PATCH] selinux: cleanup selinux_lsm_getattr()
Date: Tue, 26 Mar 2024 16:37:44 -0400 [thread overview]
Message-ID: <def2ded6147dcdf035c88a11ef98767d@paul-moore.com> (raw)
In-Reply-To: <20240223212640.305789-2-paul@paul-moore.com>
On Feb 23, 2024 Paul Moore <paul@paul-moore.com> wrote:
>
> A number of small changes to selinux_lsm_getattr() to improve the
> quality and readability of the code:
>
> * Explicitly set the `value` parameter to NULL in the case where an
> attribute has not been set.
> * Rename the `__tsec` variable to `tsec` to better fit the SELinux code.
> * Rename `bad` to `err_unlock` to better indicate the jump target drops
> the RCU lock.
>
> Signed-off-by: Paul Moore <paul@paul-moore.com>
> ---
> security/selinux/hooks.c | 36 ++++++++++++++++++------------------
> 1 file changed, 18 insertions(+), 18 deletions(-)
Merged into selinux/dev.
--
paul-moore.com
prev parent reply other threads:[~2024-03-26 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 21:26 [PATCH] selinux: cleanup selinux_lsm_getattr() Paul Moore
2024-03-26 20:37 ` Paul Moore [this message]
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=def2ded6147dcdf035c88a11ef98767d@paul-moore.com \
--to=paul@paul-moore.com \
--cc=selinux@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).