From: Paul Moore <paul@paul-moore.com>
To: Khadija Kamran <kamrankhadijadj@gmail.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
ztarkhani@microsoft.com, James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lsm: add comment block for security_sk_classify_flow LSM hook
Date: Mon, 31 Jul 2023 16:07:38 -0400 [thread overview]
Message-ID: <abe91475c7f9e3483405c6096006b2a9.paul@paul-moore.com> (raw)
In-Reply-To: <ZMfG/w5FWqCGE4pn@gmail.com>
On Jul 31, 2023 Khadija Kamran wrote:
>
> 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.
>
> Signed-off-by: Khadija Kamran <kamrankhadijadj@gmail.com>
> ---
> security/security.c | 7 +++++++
> 1 file changed, 7 insertions(+)
Thanks Khadija. I did make a small change to your patch (see below)
when merging it into the lsm/next branch.
> 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
As has been pointed out previously, there is a double-space between
"sk:" and "original socket".
> + * @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
--
paul-moore.com
prev parent reply other threads:[~2023-07-31 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 14:36 Khadija Kamran
2023-07-31 16:56 ` Alison Schofield
2023-08-07 6:27 ` Khadija Kamran
2023-07-31 20:07 ` 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=abe91475c7f9e3483405c6096006b2a9.paul@paul-moore.com \
--to=paul@paul-moore.com \
--cc=alison.schofield@intel.com \
--cc=jmorris@namei.org \
--cc=kamrankhadijadj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=ztarkhani@microsoft.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
all inboxes | Powered by JetHome®