From: efremov@linux.com
To: James Morris <jmorris@namei.org>
Cc: Denis Efremov <efremov@linux.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Eric Paris <eparis@redhat.com>, Paul Moore <paul@paul-moore.com>,
Kees Cook <keescook@chromium.org>,
John Johansen <john.johansen@canonical.com>,
Catherine Zhang <cxzhang@watson.ibm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] security: fix documentation for the socket_getpeersec_dgram hook
Date: Tue, 23 Oct 2018 14:14:50 +0300 [thread overview]
Message-ID: <20181023111450.31837-1-efremov@linux.com> (raw)
From: Denis Efremov <efremov@linux.com>
The socket_getpeersec_dgram hook was changed in the commit
"[AF_UNIX]: Kernel memory leak fix for af_unix datagram getpeersec patch"
(dc49c1f94e34). The arguments @secdata and @seclen were changed to @sock
and @secid. This patch updates the documentation accordingly.
Signed-off-by: Denis Efremov <efremov@linux.com>
---
include/linux/lsm_hooks.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/lsm_hooks.h b/include/linux/lsm_hooks.h
index ae3766720264..a598e601ccb3 100644
--- a/include/linux/lsm_hooks.h
+++ b/include/linux/lsm_hooks.h
@@ -861,9 +861,9 @@
* the IP_PASSSEC option via getsockopt. It can then retrieve the
* security state returned by this hook for a packet via the SCM_SECURITY
* ancillary message type.
- * @skb is the skbuff for the packet being queried
- * @secdata is a pointer to a buffer in which to copy the security data
- * @seclen is the maximum length for @secdata
+ * @sock contains the socket structure.
+ * @skb is the skbuff for the packet being queried.
+ * @secid: pointer to where to put the secid of the packet.
* Return 0 on success, error on failure.
* @sk_alloc_security:
* Allocate and attach a security structure to the sk->sk_security field,
--
2.17.2
next reply other threads:[~2018-10-23 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 11:14 efremov [this message]
2018-10-23 19:28 ` [PATCH] security: fix documentation for the socket_getpeersec_dgram hook Kees Cook
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=20181023111450.31837-1-efremov@linux.com \
--to=efremov@linux.com \
--cc=cxzhang@watson.ibm.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@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