linux-kernel - Re: [PATCH 3/9] security: fix documentation for the socket_post

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAGXu5j+nJM6RWZJZNBsvVSbS7=UkyGFEnO_rM+phFtLvxYuRYA@mail.gmail.com>
Date:   Tue, 23 Oct 2018 12:28:01 -0700
From:   Kees Cook <keescook@...omium.org>
To:     efremov@...ux.com
Cc:     James Morris <jmorris@...ei.org>,
        "Serge E. Hallyn" <serge@...lyn.com>,
        Eric Paris <eparis@...hat.com>,
        Paul Moore <paul@...l-moore.com>,
        John Johansen <john.johansen@...onical.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/9] security: fix documentation for the
 socket_post_create hook

On Tue, Oct 23, 2018 at 4:08 AM,  <efremov@...ux.com> wrote:
> From: Denis Efremov <efremov@...ux.com>
>
> This patch slightly fixes the documentation for the
> socket_post_create hook. The documentation states that
> i_security field is accessible through inode field of socket
> structure (i.e., 'sock->inode->i_security'). There is no inode
> field in the socket structure. The i_security field is accessible
> through SOCK_INODE macro. The patch fixes the documentation accordingly.
>
> Signed-off-by: Denis Efremov <efremov@...ux.com>

Reviewed-by: Kees Cook <keescook@...omium.org>

-Kees

> ---
>  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 8f84ef819e00..accf6f34ac8e 100644
> --- a/include/linux/lsm_hooks.h
> +++ b/include/linux/lsm_hooks.h
> @@ -752,9 +752,9 @@
>   *     socket structure, but rather, the socket security information is stored
>   *     in the associated inode.  Typically, the inode alloc_security hook will
>   *     allocate and and attach security information to
> - *     sock->inode->i_security.  This hook may be used to update the
> - *     sock->inode->i_security field with additional information that wasn't
> - *     available when the inode was allocated.
> + *     SOCK_INODE(sock)->i_security.  This hook may be used to update the
> + *     SOCK_INODE(sock)->i_security field with additional information that
> + *     wasn't available when the inode was allocated.
>   *     @sock contains the newly created socket structure.
>   *     @family contains the requested protocol family.
>   *     @type contains the requested communications type.
> --
> 2.17.2
>



-- 
Kees Cook