Thread (4 messages) 4 messages, 3 authors, 2023-08-07

Re: [PATCH] lsm: add comment block for security_sk_classify_flow LSM hook

From: Khadija Kamran <hidden>
Date: 2023-08-07 06:28:05
Also in: lkml

On Mon, Jul 31, 2023 at 09:56:04AM -0700, Alison Schofield wrote:
On Mon, Jul 31, 2023 at 07:36:47PM +0500, Khadija Kamran wrote:
quoted
security_sk_classify_flow LSM hook has no comment block. Add a comment
block with a brief description of LSM hook and its function parameters.
When referring to functions, in the one line commit message, or here
in the commit log, it is customary to add the parenthesis to be clear
it is a function name.

ie. security_sk_classify_flow()
quoted
Signed-off-by: Khadija Kamran <redacted>
---
 security/security.c | 7 +++++++
 1 file changed, 7 insertions(+)
diff --git a/security/security.c b/security/security.c
index d5ff7ff45b77..ffc5519e49cd 100644
--- a/security/security.c
+++ b/security/security.c
@@ -4396,6 +4396,13 @@ void security_sk_clone(const struct sock *sk, struct sock *newsk)
 }
 EXPORT_SYMBOL(security_sk_clone);
 
+/**
+ * security_sk_classify_flow() - Set a flow's secid based on socket
+ * @sk:  original socket
           ^errant space
Hey Alison,
Noted. Thank you.
quoted
+ * @flic: target flow
+ *
+ * Set the target flow's secid to socket's secid.
+ */
 void security_sk_classify_flow(struct sock *sk, struct flowi_common *flic)
 {
 	call_void_hook(sk_getsecid, sk, &flic->flowic_secid);
-- 
2.34.1
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help