public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Waiman Long <Waiman.Long@hp.com>,
	Paul Moore <paul@paul-moore.com>,
	Eric Paris <eparis@parisplace.org>,
	James Morris <james.l.morris@oracle.com>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	selinux@tycho.nsa.gov
Cc: Scott J Norton <scott.norton@hp.com>,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, Douglas Hatch <doug.hatch@hp.com>
Subject: Re: [PATCH] selinux: reduce locking overhead in inode_free_security()
Date: Fri, 12 Jun 2015 08:32:26 -0400	[thread overview]
Message-ID: <557AD15A.3090004@tycho.nsa.gov> (raw)
In-Reply-To: <1433967446-44555-1-git-send-email-Waiman.Long@hp.com>

On 06/10/2015 04:17 PM, Waiman Long wrote:
> The inode_free_security() function just took the superblock's isec_lock
> before checking and trying to remove the inode security struct from the
> linked list. In many cases, the list was empty and so the lock taking
> is wasteful as no useful work is done. On multi-socket systems with
> a large number of CPUs, there can also be a fair amount of spinlock
> contention on the isec_lock if many tasks are exiting at the same time.
> 
> This patch changes the code to check the state of the list first
> before taking the lock and attempting to dequeue it. We still need
> to do the empty list test inside the lock for safety reason, but it
> minimizes the chance of unnecessary spinlock contention.
> 
> Signed-off-by: Waiman Long <Waiman.Long@hp.com>

Acked-by:  Stephen Smalley <sds@tycho.nsa.gov>

> ---
>  security/selinux/hooks.c |   17 +++++++++++++----
>  1 files changed, 13 insertions(+), 4 deletions(-)
> 
> diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
> index 7dade28..cd736c3 100644
> --- a/security/selinux/hooks.c
> +++ b/security/selinux/hooks.c
> @@ -254,10 +254,19 @@ static void inode_free_security(struct inode *inode)
>  	struct inode_security_struct *isec = inode->i_security;
>  	struct superblock_security_struct *sbsec = inode->i_sb->s_security;
>  
> -	spin_lock(&sbsec->isec_lock);
> -	if (!list_empty(&isec->list))
> -		list_del_init(&isec->list);
> -	spin_unlock(&sbsec->isec_lock);
> +	/*
> +	 * As not all inode security structures are in a list, we check for
> +	 * empty list outside of the lock to make sure that we won't waste
> +	 * time taking a lock doing nothing. Lock taking can be slow
> +	 * especially if the lock is being contended. We do, however, need
> +	 * to recheck the list again before deleting it for safety.
> +	 */
> +	if (!list_empty(&isec->list)) {
> +		spin_lock(&sbsec->isec_lock);
> +		if (!list_empty(&isec->list))
> +			list_del_init(&isec->list);
> +		spin_unlock(&sbsec->isec_lock);
> +	}
>  
>  	/*
>  	 * The inode may still be referenced in a path walk and
> 


      parent reply	other threads:[~2015-06-12 12:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 20:17 [PATCH] selinux: reduce locking overhead in inode_free_security() Waiman Long
2015-06-11 12:38 ` Stephen Smalley
2015-06-11 21:17   ` Waiman Long
2015-06-12 12:32 ` Stephen Smalley [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=557AD15A.3090004@tycho.nsa.gov \
    --to=sds@tycho.nsa.gov \
    --cc=Waiman.Long@hp.com \
    --cc=doug.hatch@hp.com \
    --cc=eparis@parisplace.org \
    --cc=james.l.morris@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=scott.norton@hp.com \
    --cc=selinux@tycho.nsa.gov \
    --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