public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia@diku.dk>
To: Paul Moore <paul.moore@hp.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 4/5] net/netlabel: Add kmalloc NULL tests
Date: Thu, 30 Jul 2009 14:36:47 +0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0907301636280.8734@ask.diku.dk> (raw)
In-Reply-To: <200907301032.20318.paul.moore@hp.com>

On Thu, 30 Jul 2009, Paul Moore wrote:

> On Thursday 30 July 2009 10:10:54 am Julia Lawall wrote:
> > From: Julia Lawall <julia@diku.dk>
> >
> > The test on map4 should be a test on map6.
> 
> ...
> 
> > Signed-off-by: Julia Lawall <julia@diku.dk>
> >
> > ---
> >  net/netlabel/netlabel_kapi.c        |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/net/netlabel/netlabel_kapi.c b/net/netlabel/netlabel_kapi.c
> > index 3ff6f32..6ce0020 100644
> > --- a/net/netlabel/netlabel_kapi.c
> > +++ b/net/netlabel/netlabel_kapi.c
> > @@ -151,7 +151,7 @@ int netlbl_cfg_unlbl_map_add(const char *domain,
> >  			addr6 = addr;
> >  			mask6 = mask;
> >  			map6 = kzalloc(sizeof(*map6), GFP_ATOMIC);
> > -			if (map4 = NULL)
> > +			if (!map6)
> >  				goto cfg_unlbl_map_add_failure;
> >  			map6->type = NETLBL_NLTYPE_UNLABELED;
> >  			ipv6_addr_copy(&map6->list.addr, addr6);
> 
> Another good find, although I would suggest changing it to the following to 
> stay consistent with the rest of the function:
> 
> 		map6 = kzalloc(...);
> 		if (map6 = NULL)
> 			goto ...;

OK, I hesitated...  I'll send a new patch shortly.

julia

  reply	other threads:[~2009-07-30 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 14:10 [PATCH 4/5] net/netlabel: Add kmalloc NULL tests Julia Lawall
2009-07-30 14:32 ` Paul Moore
2009-07-30 14:36   ` Julia Lawall [this message]
2009-07-30 14:37     ` Paul Moore
2009-07-30 14:38   ` Julia Lawall
2009-07-30 14:53     ` Paul Moore
2009-07-30 17:59       ` David Miller

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=Pine.LNX.4.64.0907301636280.8734@ask.diku.dk \
    --to=julia@diku.dk \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul.moore@hp.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