public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise@opengridcomputing.com>
To: Nick Krause <xerofoify@gmail.com>, Levente Kurusa <levex@linux.com>
Cc: swise@chelsio.com, roland@kernel.org, sean.hefty@intel.com,
	hal.rosenstock@gmail.com, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3]Checks for Null value in function *get_skub
Date: Mon, 16 Jun 2014 10:18:39 -0500	[thread overview]
Message-ID: <539F0ACF.6080609@opengridcomputing.com> (raw)
In-Reply-To: <CAPDOMVg8hthn2beTjHx94RRJeRHGGP1wyT0Y2KfscUtZGFfiCA@mail.gmail.com>


On 6/16/2014 10:14 AM, Nick Krause wrote:
> >From what I know yes so I would close the bug at the the link in
> my previous email and just void my patch.
> Cheers Nick

We shouldn't be kfree-ing an skb anyway.  Should use kfree_skb().

There is still a leak if skb is non-null and the skb is non linear or 
cloned.


> On Mon, Jun 16, 2014 at 11:12 AM, Levente Kurusa <levex@linux.com> wrote:
>> On 06/16/2014 05:08 PM, Nicholas Krause wrote:
>>> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
>>> ---
>>>    drivers/infiniband/hw/cxgb4/cm.c | 8 +++-----
>>>    1 file changed, 3 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/drivers/infiniband/hw/cxgb4/cm.c
>>> b/drivers/infiniband/hw/cxgb4/cm.c
>>> index f9477e2..2d56983 100644
>>> --- a/drivers/infiniband/hw/cxgb4/cm.c
>>> +++ b/drivers/infiniband/hw/cxgb4/cm.c
>>> @@ -340,15 +340,13 @@ static int status2errno(int status)
>>>     */
>>>    static struct sk_buff *get_skb(struct sk_buff *skb, int len, gfp_t gfp)
>>>    {
>>>    if (skb && !skb_is_nonlinear(skb) && !skb_cloned(skb)) {
>>>                   skb_trim(skb, 0);
>>>                   skb_get(skb);
>>>                   skb_reset_transport_header(skb);
>>>          } else {
>>> +               if (skb)
>>> +                       kfree (skb);
>>>                  skb = alloc_skb(len, gfp);
>>>          }
>>>          t4_set_arp_err_handler(skb, NULL, NULL);
>>>
>> Isn't kfree(NULL) legal?
>>
>> (i.e. the if statement is useless)
>>
>> Thanks,
>>      Levente Kurusa


      reply	other threads:[~2014-06-16 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 15:08 [PATCHv3]Checks for Null value in function *get_skub Nicholas Krause
2014-06-16 15:10 ` Nick Krause
2014-06-16 15:12 ` Levente Kurusa
2014-06-16 15:14   ` Nick Krause
2014-06-16 15:18     ` Steve Wise [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=539F0ACF.6080609@opengridcomputing.com \
    --to=swise@opengridcomputing.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=levex@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=roland@kernel.org \
    --cc=sean.hefty@intel.com \
    --cc=swise@chelsio.com \
    --cc=xerofoify@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