From: Julia Lawall <julia@diku.dk>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Robert Love <robert.w.love@intel.com>,
kernel-janitors@vger.kernel.org,
"James E.J. Bottomley" <JBottomley@parallels.com>,
devel@open-fcoe.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] drivers/scsi/fcoe/fcoe.c: add missing test
Date: Mon, 22 Aug 2011 16:36:16 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1108221636030.10948@ask.diku.dk> (raw)
In-Reply-To: <alpine.LNX.2.00.1108221632130.9774@swampdragon.chaosbits.net>
On Mon, 22 Aug 2011, Jesper Juhl wrote:
> On Mon, 22 Aug 2011, Julia Lawall wrote:
>
> > From: Julia Lawall <julia@diku.dk>
> >
> > The initializations of both fcoe_nport_scsi_transport and
> > fcoe_vport_scsi_transport can fail, so test both of them.
> >
> > The semantic match that finds this problem is as follows:
> > (http://coccinelle.lip6.fr/)
> >
> > // <smpl>
> > @r@
> > identifier x,y,f!={PTR_ERR,ERR_PTR,ERR_CAST};
> > statement S;
> > @@
> >
> > x = f(...);
> > (
> > if (\(x == NULL\|IS_ERR(x)\)) S
> > |
> > *if (\(y == NULL\|IS_ERR(y)\))
> > { ... when != x
> > return ...; }
> > )
> > // </smpl>
> >
> > Signed-off-by: Julia Lawall <julia@diku.dk>
> >
> > ---
> > drivers/scsi/fcoe/fcoe.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/scsi/fcoe/fcoe.c b/drivers/scsi/fcoe/fcoe.c
> > index ba710e3..921b636 100644
> > --- a/drivers/scsi/fcoe/fcoe.c
> > +++ b/drivers/scsi/fcoe/fcoe.c
> > @@ -1096,7 +1096,7 @@ static int __init fcoe_if_init(void)
> > fcoe_vport_scsi_transport =
> > fc_attach_transport(&fcoe_vport_fc_functions);
> >
> > - if (!fcoe_nport_scsi_transport) {
> > + if (!fcoe_nport_scsi_transport || !fcoe_vport_scsi_transport) {
> > printk(KERN_ERR "fcoe: Failed to attach to the FC transport\n");
> > return -ENODEV;
> > }
> >
>
> I only took a quick look, so I may have overlooked something, so bear with
> me.
>
> fc_attach_transport() allocates memory with kzalloc. If either call fails
> the other may have succeeded and we'll leak the memory allocated to one of
> them.
>
> Shouldn't we be kfree()'ing the two variables before the 'return -ENODEV'?
It seems reasonable.
julia
next prev parent reply other threads:[~2011-08-22 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 14:00 Julia Lawall
2011-08-22 14:34 ` Jesper Juhl
2011-08-22 14:36 ` Julia Lawall [this message]
2011-08-22 14:49 ` Julia Lawall
2011-08-23 7:23 ` [Open-FCoE] " Zou, Yi
2011-08-23 8:33 ` Julia Lawall
2011-08-23 8:42 ` Julia Lawall
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.1108221636030.10948@ask.diku.dk \
--to=julia@diku.dk \
--cc=JBottomley@parallels.com \
--cc=devel@open-fcoe.org \
--cc=jj@chaosbits.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=robert.w.love@intel.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
all inboxes | Powered by JetHome®