public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Duan Jiong <duanj.fnst@cn.fujitsu.com>
Cc: sds@tycho.nsa.gov, james.l.morris@oracle.com,
	eparis@parisplace.org, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [PATCH] selinux: Use kmemdup instead of kmalloc + memcpy
Date: Thu, 26 Sep 2013 16:03:47 -0400	[thread overview]
Message-ID: <9522974.jAp9Aa4L2I@sifl> (raw)
In-Reply-To: <5243A058.2090104@cn.fujitsu.com>

On Thursday, September 26, 2013 10:47:52 AM Duan Jiong wrote:
> Signed-off-by: Duan Jiong <duanj.fnst@cn.fujitsu.com>
> ---
>  security/selinux/xfrm.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

FYI: SELinux patches should be sent to the SELinux mailing list (I added it to 
the CC list).  You can also CC the LSM list if you like, but they *need* to be 
sent to the SELinux list in the future.

I did some minor whitespace/alignment fixup and merged your patch; it is 
queued up for 3.13.

 * git://git.infradead.org/users/pcmoore/selinux

> diff --git a/security/selinux/xfrm.c b/security/selinux/xfrm.c
> index 425b9f9..5c809c1 100644
> --- a/security/selinux/xfrm.c
> +++ b/security/selinux/xfrm.c
> @@ -268,10 +268,10 @@ int selinux_xfrm_policy_clone(struct xfrm_sec_ctx
> *old_ctx, if (!old_ctx)
>  		return 0;
> 
> -	new_ctx = kmalloc(sizeof(*old_ctx) + old_ctx->ctx_len, GFP_ATOMIC);
> +	new_ctx = kmemdup(old_ctx, sizeof(*old_ctx) + old_ctx->ctx_len,
> +			GFP_ATOMIC);
>  	if (!new_ctx)
>  		return -ENOMEM;
> -	memcpy(new_ctx, old_ctx, sizeof(*old_ctx) + old_ctx->ctx_len);
>  	atomic_inc(&selinux_xfrm_refcount);
>  	*new_ctxp = new_ctx;

-- 
paul moore
www.paul-moore.com


      reply	other threads:[~2013-09-26 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26  2:47 [PATCH] selinux: Use kmemdup instead of kmalloc + memcpy Duan Jiong
2013-09-26 20:03 ` Paul Moore [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=9522974.jAp9Aa4L2I@sifl \
    --to=paul@paul-moore.com \
    --cc=duanj.fnst@cn.fujitsu.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=sds@tycho.nsa.gov \
    --cc=selinux@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