From: Andrew Morton <akpm@osdl.org>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, sds@tycho.nsa.gov,
James Morris <jmorris@redhat.com>
Subject: Re: [PATCH] SELinux: 3/3 convert sbsec semaphore to a mutex
Date: Wed, 23 Aug 2006 14:04:40 -0700 [thread overview]
Message-ID: <20060823140440.92bc9a10.akpm@osdl.org> (raw)
In-Reply-To: <1156362637.6662.51.camel@localhost.localdomain>
On Wed, 23 Aug 2006 15:50:37 -0400
Eric Paris <eparis@redhat.com> wrote:
> This patch converts the semaphore in the superblock security struct to a
> mutex. No locking changes or other code changes are done.
>
> This is being targeted for 2.6.19
>
> Signed-off-by: Eric Paris <eparis@redhat.com>
> Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
>
> security/selinux/hooks.c | 7 +++----
> security/selinux/include/objsec.h | 2 +-
> 2 files changed, 4 insertions(+), 5 deletions(-)
>
> --- linux-2.6-sem-changes/security/selinux/include/objsec.h.patch3 2006-08-03 14:04:07.000000000 -0400
> +++ linux-2.6-sem-changes/security/selinux/include/objsec.h 2006-08-03 14:18:44.000000000 -0400
> @@ -63,7 +63,7 @@ struct superblock_security_struct {
> unsigned int behavior; /* labeling behavior */
> unsigned char initialized; /* initialization flag */
> unsigned char proc; /* proc fs */
> - struct semaphore sem;
> + struct mutex lock;
> struct list_head isec_head;
> spinlock_t isec_lock;
> };
> --- linux-2.6-sem-changes/security/selinux/hooks.c.patch3 2006-08-02 14:29:28.000000000 -0400
> +++ linux-2.6-sem-changes/security/selinux/hooks.c 2006-08-03 14:21:48.000000000 -0400
> @@ -49,7 +49,6 @@
> #include <net/ip.h> /* for sysctl_local_port_range[] */
> #include <net/tcp.h> /* struct or_callable used in sock_rcv_skb */
> #include <asm/uaccess.h>
> -#include <asm/semaphore.h>
> #include <asm/ioctls.h>
> #include <linux/bitops.h>
> #include <linux/interrupt.h>
> @@ -240,7 +239,7 @@ static int superblock_alloc_security(str
> if (!sbsec)
> return -ENOMEM;
>
> - init_MUTEX(&sbsec->sem);
> + mutex_init(&sbsec->lock);
> INIT_LIST_HEAD(&sbsec->list);
> INIT_LIST_HEAD(&sbsec->isec_head);
> spin_lock_init(&sbsec->isec_lock);
> @@ -595,7 +594,7 @@ static int superblock_doinit(struct supe
> struct inode *inode = root->d_inode;
> int rc = 0;
>
> - down(&sbsec->sem);
> + mutex_lock(&sbsec->lock);
> if (sbsec->initialized)
> goto out;
>
> @@ -690,7 +689,7 @@ next_inode:
> }
> spin_unlock(&sbsec->isec_lock);
> out:
> - up(&sbsec->sem);
> + mutex_unlock(&sbsec->lock);
> return rc;
> }
>
>
Does this lock actually do anything?
next prev parent reply other threads:[~2006-08-23 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 19:50 Eric Paris
2006-08-23 20:05 ` James Morris
2006-08-23 21:04 ` Andrew Morton [this message]
2006-08-24 12:32 ` Stephen Smalley
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=20060823140440.92bc9a10.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=eparis@redhat.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
/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
all inboxes | Powered by JetHome®