From: Pairman Guo <pairmanxlr@gmail.com>
To: paul@paul-moore.com
Cc: jmorris@namei.org, serge@hallyn.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Pairman Guo <pairmanxlr@gmail.com>
Subject: [PATCH] LSM: Fix typos in security/security.c comment headers
Date: Sat, 17 Feb 2024 21:35:04 +0800 [thread overview]
Message-ID: <20240217133504.4534-1-pairmanxlr@gmail.com> (raw)
This commit fixes several typos in comment headers in security/security.c
where "Check is" should be "Check if".
Signed-off-by: Pairman Guo <pairmanxlr@gmail.com>
---
security/security.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/security/security.c b/security/security.c
index 7035ee35a..0bd3e9df4 100644
--- a/security/security.c
+++ b/security/security.c
@@ -2904,7 +2904,7 @@ int security_file_send_sigiotask(struct task_struct *tsk,
}
/**
- * security_file_receive() - Check is receiving a file via IPC is allowed
+ * security_file_receive() - Check if receiving a file via IPC is allowed
* @file: file being received
*
* This hook allows security modules to control the ability of a process to
@@ -3114,7 +3114,7 @@ int security_kernel_create_files_as(struct cred *new, struct inode *inode)
}
/**
- * security_kernel_module_request() - Check is loading a module is allowed
+ * security_kernel_module_request() - Check if loading a module is allowed
* @kmod_name: module name
*
* Ability to trigger the kernel to automatically upcall to userspace for
@@ -4114,7 +4114,7 @@ int security_netlink_send(struct sock *sk, struct sk_buff *skb)
}
/**
- * security_ismaclabel() - Check is the named attribute is a MAC label
+ * security_ismaclabel() - Check if the named attribute is a MAC label
* @name: full extended attribute name
*
* Check if the extended attribute specified by @name represents a MAC label.
@@ -4487,7 +4487,7 @@ int security_socket_accept(struct socket *sock, struct socket *newsock)
}
/**
- * security_socket_sendmsg() - Check is sending a message is allowed
+ * security_socket_sendmsg() - Check if sending a message is allowed
* @sock: sending socket
* @msg: message to send
* @size: size of message
--
2.43.2
next reply other threads:[~2024-02-17 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 13:35 Pairman Guo [this message]
2024-02-22 0:03 ` [PATCH] LSM: Fix typos in security/security.c comment headers Paul Moore
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=20240217133504.4534-1-pairmanxlr@gmail.com \
--to=pairmanxlr@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
/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).