History

LSM: fix documentation for the socket_post_create hook

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 updates the documentation to reflect this.

Denis Efremov committed 7 years ago

Commit 68b3edb1 parent 5f4b9751 file · +3 −3Browse files

Showing the changes to include/linux (1 of 1 file). Show all

Unified · Split

include/linux/lsm_hooks.h+3−3
@@ -768,9 +768,9 @@ · 767 unmodified lines
768768 * socket structure, but rather, the socket security information is stored
769769 * in the associated inode. Typically, the inode alloc_security hook will
770770 * allocate and and attach security information to
771− * sock->inode->i_security. This hook may be used to update the
772− * sock->inode->i_security field with additional information that wasn't
773− * available when the inode was allocated.
771+ * SOCK_INODE(sock)->i_security. This hook may be used to update the
772+ * SOCK_INODE(sock)->i_security field with additional information that
773+ * wasn't available when the inode was allocated.
774774 * @sock contains the newly created socket structure.
775775 * @family contains the requested protocol family.
776776 * @type contains the requested communications type.

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t