All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: wen.yang99@zte.com.cn
Cc: linux-kernel@vger.kernel.org, wang.yi59@zte.com.cn,
	dougmill@linux.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH 2/3] net: ibm: fix possible object reference leak
Date: Sat, 23 Mar 2019 21:21:55 -0400 (EDT)	[thread overview]
Message-ID: <20190323.212155.1537951760061802531.davem@davemloft.net> (raw)
In-Reply-To: <1553223849-7143-2-git-send-email-wen.yang99@zte.com.cn>

From: Wen Yang <wen.yang99@zte.com.cn>
Date: Fri, 22 Mar 2019 11:04:08 +0800

> The call to ehea_get_eth_dn returns a node pointer with refcount
> incremented thus it must be explicitly decremented after the last
> usage.
> 
> Detected by coccinelle with the following warnings:
> ./drivers/net/ethernet/ibm/ehea/ehea_main.c:3163:2-8: ERROR: missing of_node_put; acquired a node pointer with refcount incremented on line 3154, but without a corresponding object release within this function.
> 
> Signed-off-by: Wen Yang <wen.yang99@zte.com.cn>

Applied.

  reply	other threads:[~2019-03-24  1:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22  3:04 [PATCH 1/3] net: xilinx: fix possible object reference leak Wen Yang
2019-03-22  3:04 ` Wen Yang
2019-03-22  3:04 ` [PATCH 2/3] net: ibm: " Wen Yang
2019-03-24  1:21   ` David Miller [this message]
2019-03-22  3:04 ` [PATCH 3/3] net: ethernet: ti: " Wen Yang
2019-03-24  1:22   ` David Miller
2019-04-05  8:27   ` [PATCH 3/3] " Markus Elfring
2019-04-05  8:27     ` Markus Elfring
2019-03-24  1:21 ` [PATCH 1/3] net: xilinx: " David Miller
2019-03-24  1:21   ` David Miller
2019-04-05  7:54 ` Markus Elfring
2019-04-05  7:54   ` Markus Elfring
2019-04-05  7:54   ` Markus Elfring
2019-04-05  8:13   ` Dan Carpenter
2019-04-05  8:13     ` Dan Carpenter
2019-04-05  8:13     ` Dan Carpenter
2019-04-05  9:18     ` [1/3] " Markus Elfring
2019-04-05  9:18       ` Markus Elfring

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=20190323.212155.1537951760061802531.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dougmill@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wang.yi59@zte.com.cn \
    --cc=wen.yang99@zte.com.cn \
    /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.