All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Remove extraneous function gfs2_security_init
Date: Wed, 19 Mar 2014 15:21:41 +0000	[thread overview]
Message-ID: <1395242501.2749.10.camel@menhir> (raw)
In-Reply-To: <3657907.2015659.1395236220720.JavaMail.zimbra@redhat.com>

Hi,

Both patches now in the -nmw tree. Thanks,

Steve.

On Wed, 2014-03-19 at 09:37 -0400, Bob Peterson wrote:
> Hi,
> 
> This patch eliminates function gfs2_security_init in favor of just
> calling security_inode_init_security directly.
> 
> Regards,
> 
> Bob Peterson
> Red Hat File Systems
> 
> Signed-off-by: Bob Peterson <rpeterso@redhat.com> 
> ---
> diff --git a/fs/gfs2/inode.c b/fs/gfs2/inode.c
> index ec455b9..e790949 100644
> --- a/fs/gfs2/inode.c
> +++ b/fs/gfs2/inode.c
> @@ -571,13 +571,6 @@ static int gfs2_initxattrs(struct inode *inode, const struct xattr *xattr_array,
>  	return err;
>  }
>  
> -static int gfs2_security_init(struct gfs2_inode *dip, struct gfs2_inode *ip,
> -			      const struct qstr *qstr)
> -{
> -	return security_inode_init_security(&ip->i_inode, &dip->i_inode, qstr,
> -					    &gfs2_initxattrs, NULL);
> -}
> -
>  /**
>   * gfs2_create_inode - Create a new inode
>   * @dir: The parent directory
> @@ -758,7 +751,8 @@ static int gfs2_create_inode(struct inode *dir, struct dentry *dentry,
>  	if (error)
>  		goto fail_gunlock3;
>  
> -	error = gfs2_security_init(dip, ip, name);
> +	error = security_inode_init_security(&ip->i_inode, &dip->i_inode, name,
> +					     &gfs2_initxattrs, NULL);
>  	if (error)
>  		goto fail_gunlock3;
>  
> 




      reply	other threads:[~2014-03-19 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49650852.2014435.1395236099773.JavaMail.zimbra@redhat.com>
2014-03-19 13:37 ` [Cluster-devel] [GFS2 PATCH] GFS2: Remove extraneous function gfs2_security_init Bob Peterson
2014-03-19 15:21   ` Steven Whitehouse [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=1395242501.2749.10.camel@menhir \
    --to=swhiteho@redhat.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 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.