public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@emulex.com>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: "syamsidhardh@gmail.com" <syamsidhardh@gmail.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"JBottomley@parallels.com" <JBottomley@parallels.com>,
	Syam Sidhardhan <s.syam@samsung.com>
Subject: Re: [PATCH v1] lpfc 8.3.37: Remove redundant NULL check before kfree
Date: Thu, 7 Mar 2013 13:05:59 -0500	[thread overview]
Message-ID: <5138D707.8060904@emulex.com> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402950DA4F5D@G9W0745.americas.hpqcorp.net>

I don't disagree.    My intent would be it is all one way - with my 
leaning toward being explicit.  Unfortunately, it's a low priority task.

-- james s


On 3/6/2013 6:32 PM, Elliott, Robert (Server Storage) wrote:
> If the other approach is taken, then not all kfree() calls are protected by a NULL check.
>
> One example in lpfc_els.c (from 3.7-rc5):
> 	if (!pbuflist || !pbuflist->virt)
> 		goto els_iocb_free_pbuf_exit;
> ...
> els_iocb_free_pbuf_exit:
> 	if (expectRsp)
> 		lpfc_mbuf_free(phba, prsp->virt, prsp->phys);
> 	kfree(pbuflist);
>
>
>
>
>> -----Original Message-----
>> From: linux-scsi-owner@vger.kernel.org [mailto:linux-scsi-
>> owner@vger.kernel.org] On Behalf Of James Smart
>> Sent: Wednesday, 06 March, 2013 3:10 PM
>> To: syamsidhardh@gmail.com
>> Cc: linux-scsi@vger.kernel.org; JBottomley@parallels.com; Syam Sidhardhan;
>> Smart, James
>> Subject: Re: [PATCH v1] lpfc 8.3.37: Remove redundant NULL check before
>> kfree
>>
>> Syam,
>>
>> Thank you for the patch - it is valid.
>>
>> However, I prefer not to merge this.  I would rather force the coder to
>> think about the pointer value explicitly rather than depending on the
>> convenience/one line optimization.  We've had errors in the past covered
>> up by this gracious behavior.  Additionally, we have coders that work on
>> linux and vmware, and the semantics of the kfree() routine differ.   For
>> now, I'd prefer to stay as is and force good habits.
>>
>> -- james s
>>
>>
>> On 3/6/2013 3:12 PM, syamsidhardh@gmail.com wrote:
>>> From: Syam Sidhardhan <s.syam@samsung.com>
>>>
>>> kfree on NULL pointer is a no-op.
>>>
>>> Signed-off-by: Syam Sidhardhan <s.syam@samsung.com>
>>> ---
>>> v1-> Corrected the from address.
>>>
>>>    drivers/scsi/lpfc/lpfc_bsg.c |    3 +--
>>>    1 file changed, 1 insertion(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/scsi/lpfc/lpfc_bsg.c b/drivers/scsi/lpfc/lpfc_bsg.c
>>> index 32d5683..2166097 100644
>>> --- a/drivers/scsi/lpfc/lpfc_bsg.c
>>> +++ b/drivers/scsi/lpfc/lpfc_bsg.c
>>> @@ -1129,8 +1129,7 @@ lpfc_bsg_hba_set_event(struct fc_bsg_job *job)
>>>    	return 0; /* call job done later */
>>>
>>>    job_error:
>>> -	if (dd_data != NULL)
>>> -		kfree(dd_data);
>>> +	kfree(dd_data);
>>>
>>>    	job->dd_data = NULL;
>>>    	return rc;
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>


      reply	other threads:[~2013-03-07 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 20:12 [PATCH v1] lpfc 8.3.37: Remove redundant NULL check before kfree syamsidhardh
2013-03-06 21:10 ` James Smart
2013-03-06 23:32   ` Elliott, Robert (Server Storage)
2013-03-07 18:05     ` James Smart [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=5138D707.8060904@emulex.com \
    --to=james.smart@emulex.com \
    --cc=Elliott@hp.com \
    --cc=JBottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=s.syam@samsung.com \
    --cc=syamsidhardh@gmail.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