From: Levente Kurusa <levex@linux.com>
To: Nick Krause <xerofoify@gmail.com>,
Steve Wise <swise@opengridcomputing.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: [PATCHv4]Checks for Null value in function *get_skub
Date: Mon, 16 Jun 2014 17:45:51 +0200 [thread overview]
Message-ID: <539F112F.7030303@linux.com> (raw)
In-Reply-To: <CAPDOMVjd9J=Kz4d88==UsbfjH13mhGzzmbc2NnxSOfqJs_aGpQ@mail.gmail.com>
On 06/16/2014 05:37 PM, Nick 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)
> /* NULL is ignored */.
> + kfree_skb (skb);
> skb = alloc_skb(len, gfp);
> }
> t4_set_arp_err_handler(skb, NULL, NULL);
This patch is severely whitespace damaged. Can you fix your MUA
or try to use git-send-email?
The changelog as well is of low quality. Maybe something like this:
infiniband: cxgb4: fix memory skb memory leak
... would be better.
Also, this fails the build, due to the extra dot character after
the comment. :-(
Thanks,
Levente Kurusa.
next prev parent reply other threads:[~2014-06-16 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 15:25 [PATCHv4]Checks for Null value in function *get_skub Nicholas Krause
[not found] ` <1402932328-3732-1-git-send-email-xerofoify-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-16 15:30 ` Steve Wise
2014-06-16 15:30 ` Steve Wise
[not found] ` <539F0DAF.1020802-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2014-06-16 15:33 ` Levente Kurusa
2014-06-16 15:33 ` Levente Kurusa
2014-06-16 15:37 ` Nick Krause
2014-06-16 15:37 ` Nick Krause
[not found] ` <CAPDOMVjd9J=Kz4d88==UsbfjH13mhGzzmbc2NnxSOfqJs_aGpQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-16 15:45 ` Nick Krause
2014-06-16 15:45 ` Nick Krause
[not found] ` <CAPDOMVh4iBhWe50LZtiotpgWBn3fhX1jofyeAeYW4kHxx+Q4FQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-16 17:18 ` Steve Wise
2014-06-16 17:18 ` Steve Wise
2014-06-16 15:45 ` Levente Kurusa [this message]
[not found] ` <539F112F.7030303-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
2014-06-16 16:32 ` Nick Krause
2014-06-16 16:32 ` Nick Krause
2014-06-16 16:37 ` Steve Wise
2014-06-16 16:37 ` Steve Wise
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=539F112F.7030303@linux.com \
--to=levex@linux.com \
--cc=hal.rosenstock@gmail.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=swise@opengridcomputing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.