From: Casey Schaufler <casey@schaufler-ca.com>
To: Marcin Lis <m.lis@samsung.com>,
James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Rafal Krypa <r.krypa@samsung.com>,
linux-security-module@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Marcin Lis <marcin.lis.dev@gmail.com>
Subject: Re: [PATCH 1/1] Smack: Assign smack_known_web as default smk_in label for kernel thread's socket
Date: Wed, 25 Mar 2015 07:44:15 -0700 [thread overview]
Message-ID: <5512C9BF.6020103@schaufler-ca.com> (raw)
In-Reply-To: <1421937633-2041-1-git-send-email-m.lis@samsung.com>
On 1/22/2015 6:40 AM, Marcin Lis wrote:
> This change fixes the bug associated with sockets owned by kernel threads. These
> sockets, created usually by network devices' drivers tasks, received smk_in
> label from the task that created them - the "floor" label in the most cases. The
> result was that they were not able to receive data packets because of missing
> smack rules. The main reason of the access deny is that the socket smk_in label
> is placed as the object during smk check, kernel thread's capabilities are
> omitted.
>
> Signed-off-by: Marcin Lis <m.lis@samsung.com>
Applied to git://git.gitorious.org/smack-next/kernel.git#smack-for-4.1
> ---
> security/smack/smack_lsm.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/security/smack/smack_lsm.c b/security/smack/smack_lsm.c
> index a688f7b..535a06a 100644
> --- a/security/smack/smack_lsm.c
> +++ b/security/smack/smack_lsm.c
> @@ -2452,7 +2452,20 @@ static int smack_inode_setsecurity(struct inode *inode, const char *name,
> static int smack_socket_post_create(struct socket *sock, int family,
> int type, int protocol, int kern)
> {
> - if (family != PF_INET || sock->sk == NULL)
> + struct socket_smack *ssp;
> +
> + if (sock->sk == NULL)
> + return 0;
> +
> + /*
> + * Sockets created by kernel threads receive web label.
> + */
> + if (unlikely(current->flags & PF_KTHREAD)) {
> + ssp = sock->sk->sk_security;
> + ssp->smk_in = &smack_known_web;
> + }
> +
> + if (family != PF_INET)
> return 0;
> /*
> * Set the outbound netlbl.
prev parent reply other threads:[~2015-03-25 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 14:40 [PATCH 1/1] Smack: Assign smack_known_web as default smk_in label for kernel thread's socket Marcin Lis
2015-03-25 14:44 ` Casey Schaufler [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=5512C9BF.6020103@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=m.lis@samsung.com \
--cc=marcin.lis.dev@gmail.com \
--cc=r.krypa@samsung.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