netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH 1/1 net-2.6.26] [XFRM]: Compilation warnings in xfrm_user.c.
Date: Mon, 14 Apr 2008 10:35:46 -0400	[thread overview]
Message-ID: <200804141035.46671.paul.moore@hp.com> (raw)
In-Reply-To: <1208178219-18754-1-git-send-email-den@openvz.org>

On Monday 14 April 2008 9:03:39 am Denis V. Lunev wrote:
> When CONFIG_SECURITY_NETWORK_XFRM is undefined the following warnings
> appears: net/xfrm/xfrm_user.c: In function 'xfrm_add_pol_expire':
> net/xfrm/xfrm_user.c:1576: warning: 'ctx' may be used uninitialized
> in this function net/xfrm/xfrm_user.c: In function 'xfrm_get_policy':
> net/xfrm/xfrm_user.c:1340: warning: 'ctx' may be used uninitialized
> in this function (security_xfrm_policy_alloc is noop for the case).
>
> It seems that they are result of the commit
> 03e1ad7b5d871d4189b1da3125c2f12d1b5f7d0b
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> ---
>  net/xfrm/xfrm_user.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/net/xfrm/xfrm_user.c b/net/xfrm/xfrm_user.c
> index b822b56..1810f56 100644
> --- a/net/xfrm/xfrm_user.c
> +++ b/net/xfrm/xfrm_user.c
> @@ -1343,14 +1343,14 @@ static int xfrm_get_policy(struct sk_buff
> *skb, struct nlmsghdr *nlh, if (err)
>  			return err;
>
> +		ctx = NULL;
>  		if (rt) {
>  			struct xfrm_user_sec_ctx *uctx = nla_data(rt);
>
>  			err = security_xfrm_policy_alloc(&ctx, uctx);
>  			if (err)
>  				return err;
> -		} else
> -			ctx = NULL;
> +		}
>  		xp = xfrm_policy_bysel_ctx(type, p->dir, &p->sel, ctx,
>  					   delete, &err);
>  		security_xfrm_policy_free(ctx);

Thanks for catching this, I was focusing more on the runtime issues with 
the else statement and forgot about compile time issues.  I wonder if 
it would be better to fix this in the dummy function for 
security_xfrm_policy_alloc()?  It seems cleaner to me.

-- 
paul moore
linux @ hp

  reply	other threads:[~2008-04-14 14:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 13:03 [PATCH 1/1 net-2.6.26] [XFRM]: Compilation warnings in xfrm_user.c Denis V. Lunev
2008-04-14 14:35 ` Paul Moore [this message]
2008-04-14 21:52   ` David Miller
2008-04-14 21:48 ` David Miller
2008-04-15  5:48   ` Denis V. Lunev

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=200804141035.46671.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=davem@davemloft.net \
    --cc=den@openvz.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).