From: David Howells <dhowells@redhat.com>
To: Richard A Nelson <cowboy@linux.vnet.ibm.com>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org,
openafs-devel-UX5vO7D78FVAfugRpC6u6w@public.gmane.org
Subject: Re: NFS/AFS/Selinux issues with 2.26.29
Date: Thu, 26 Mar 2009 20:55:21 +0000 [thread overview]
Message-ID: <17949.1238100921@redhat.com> (raw)
In-Reply-To: <49CAAB9B.5070104@linux.vnet.ibm.com>
Richard A Nelson <cowboy@linux.vnet.ibm.com> wrote:
> Mar 24 21:09:20 el-ghor kernel: IP: [<ffffffff803628b7>] inode_has_perm+0x2c/0x72
> ...
> Mar 24 14:33:54 bandit-hall kernel: IP: [<c021ba99>] selinux_key_alloc+0x26/0x3b
This looks suspiciously like current->cred->security might be NULL. Can you
try running with the attached patch applied to your kernel?
David
---
diff --git a/kernel/cred.c b/kernel/cred.c
index 3a03918..67f4de9 100644
--- a/kernel/cred.c
+++ b/kernel/cred.c
@@ -157,6 +157,9 @@ struct cred *prepare_creds(void)
if (security_prepare_creds(new, old, GFP_KERNEL) < 0)
goto error;
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!new->security);
+#endif
return new;
error:
@@ -250,6 +253,9 @@ struct cred *prepare_usermodehelper_creds(void)
#endif
if (security_prepare_creds(new, &init_cred, GFP_ATOMIC) < 0)
goto error;
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!new->security);
+#endif
BUG_ON(atomic_read(&new->usage) != 1);
return new;
@@ -331,6 +337,9 @@ int copy_creds(struct task_struct *p, unsigned long clone_flags)
atomic_inc(&new->user->processes);
p->cred = p->real_cred = get_cred(new);
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!new->security);
+#endif
return 0;
error_put:
@@ -360,6 +369,9 @@ int commit_creds(struct cred *new)
BUG_ON(task->cred != task->real_cred);
BUG_ON(atomic_read(&task->real_cred->usage) < 2);
BUG_ON(atomic_read(&new->usage) < 1);
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!new->security);
+#endif
old = task->real_cred;
security_commit_creds(new, old);
@@ -444,6 +456,10 @@ const struct cred *override_creds(const struct cred *new)
{
const struct cred *old = current->cred;
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!old->security);
+ WARN_ON(!new->security);
+#endif
rcu_assign_pointer(current->cred, get_cred(new));
return old;
}
@@ -460,6 +476,10 @@ void revert_creds(const struct cred *old)
{
const struct cred *override = current->cred;
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!old->security);
+ WARN_ON(!override->security);
+#endif
rcu_assign_pointer(current->cred, old);
put_cred(override);
}
@@ -507,6 +527,10 @@ struct cred *prepare_kernel_cred(struct task_struct *daemon)
else
old = get_cred(&init_cred);
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!old->security);
+#endif
+
*new = *old;
get_uid(new->user);
get_group_info(new->group_info);
@@ -527,6 +551,9 @@ struct cred *prepare_kernel_cred(struct task_struct *daemon)
atomic_set(&new->usage, 1);
put_cred(old);
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!new->security);
+#endif
return new;
error:
diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
index 7c52ba2..25bb304 100644
--- a/security/selinux/hooks.c
+++ b/security/selinux/hooks.c
@@ -3236,7 +3236,7 @@ static int selinux_task_create(unsigned long clone_flags)
static void selinux_cred_free(struct cred *cred)
{
struct task_security_struct *tsec = cred->security;
- cred->security = NULL;
+ cred->security = (void *) 0x7UL;
kfree(tsec);
}
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Richard A Nelson <cowboy@linux.vnet.ibm.com>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org, openafs-devel@openafs.org
Subject: Re: NFS/AFS/Selinux issues with 2.26.29
Date: Thu, 26 Mar 2009 20:55:21 +0000 [thread overview]
Message-ID: <17949.1238100921@redhat.com> (raw)
In-Reply-To: <49CAAB9B.5070104@linux.vnet.ibm.com>
Richard A Nelson <cowboy@linux.vnet.ibm.com> wrote:
> Mar 24 21:09:20 el-ghor kernel: IP: [<ffffffff803628b7>] inode_has_perm+0x2c/0x72
> ...
> Mar 24 14:33:54 bandit-hall kernel: IP: [<c021ba99>] selinux_key_alloc+0x26/0x3b
This looks suspiciously like current->cred->security might be NULL. Can you
try running with the attached patch applied to your kernel?
David
---
diff --git a/kernel/cred.c b/kernel/cred.c
index 3a03918..67f4de9 100644
--- a/kernel/cred.c
+++ b/kernel/cred.c
@@ -157,6 +157,9 @@ struct cred *prepare_creds(void)
if (security_prepare_creds(new, old, GFP_KERNEL) < 0)
goto error;
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!new->security);
+#endif
return new;
error:
@@ -250,6 +253,9 @@ struct cred *prepare_usermodehelper_creds(void)
#endif
if (security_prepare_creds(new, &init_cred, GFP_ATOMIC) < 0)
goto error;
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!new->security);
+#endif
BUG_ON(atomic_read(&new->usage) != 1);
return new;
@@ -331,6 +337,9 @@ int copy_creds(struct task_struct *p, unsigned long clone_flags)
atomic_inc(&new->user->processes);
p->cred = p->real_cred = get_cred(new);
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!new->security);
+#endif
return 0;
error_put:
@@ -360,6 +369,9 @@ int commit_creds(struct cred *new)
BUG_ON(task->cred != task->real_cred);
BUG_ON(atomic_read(&task->real_cred->usage) < 2);
BUG_ON(atomic_read(&new->usage) < 1);
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!new->security);
+#endif
old = task->real_cred;
security_commit_creds(new, old);
@@ -444,6 +456,10 @@ const struct cred *override_creds(const struct cred *new)
{
const struct cred *old = current->cred;
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!old->security);
+ WARN_ON(!new->security);
+#endif
rcu_assign_pointer(current->cred, get_cred(new));
return old;
}
@@ -460,6 +476,10 @@ void revert_creds(const struct cred *old)
{
const struct cred *override = current->cred;
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!old->security);
+ WARN_ON(!override->security);
+#endif
rcu_assign_pointer(current->cred, old);
put_cred(override);
}
@@ -507,6 +527,10 @@ struct cred *prepare_kernel_cred(struct task_struct *daemon)
else
old = get_cred(&init_cred);
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!old->security);
+#endif
+
*new = *old;
get_uid(new->user);
get_group_info(new->group_info);
@@ -527,6 +551,9 @@ struct cred *prepare_kernel_cred(struct task_struct *daemon)
atomic_set(&new->usage, 1);
put_cred(old);
+#ifdef CONFIG_SECURITY_SELINUX
+ WARN_ON(!new->security);
+#endif
return new;
error:
diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
index 7c52ba2..25bb304 100644
--- a/security/selinux/hooks.c
+++ b/security/selinux/hooks.c
@@ -3236,7 +3236,7 @@ static int selinux_task_create(unsigned long clone_flags)
static void selinux_cred_free(struct cred *cred)
{
struct task_security_struct *tsec = cred->security;
- cred->security = NULL;
+ cred->security = (void *) 0x7UL;
kfree(tsec);
}
next prev parent reply other threads:[~2009-03-26 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 22:09 NFS/AFS/Selinux issues with 2.26.29 Richard A Nelson
2009-03-25 22:09 ` Richard A Nelson
2009-03-25 22:33 ` Trond Myklebust
2009-03-25 22:33 ` Trond Myklebust
[not found] ` <1238020424.26487.81.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-03-26 0:42 ` Richard A Nelson
2009-03-26 0:42 ` Richard A Nelson
2009-03-26 19:40 ` Trond Myklebust
2009-03-26 19:40 ` Trond Myklebust
2009-03-25 23:24 ` Marc Dionne
2009-03-25 23:24 ` Marc Dionne
2009-03-26 20:55 ` David Howells [this message]
2009-03-26 20:55 ` David Howells
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=17949.1238100921@redhat.com \
--to=dhowells@redhat.com \
--cc=cowboy@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=openafs-devel-UX5vO7D78FVAfugRpC6u6w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.