LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "wanghai (M)" <wanghai26@huawei.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	"Tobin C. Harding" <tobin@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tyler Hicks <tyhicks@canonical.com>,
	"Ido Schimmel" <idosch@mellanox.com>,
	Alexander Duyck <alexander.h.duyck@intel.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	YueHaibing <yuehaibing@huawei.com>,
	Amritha Nambiar <amritha.nambiar@intel.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] net-sysfs: Fix error path for kobject_init_and_add()
Date: Wed, 8 May 2019 22:52:23 +0800	[thread overview]
Message-ID: <2062f0d4-e51f-106e-cd0b-f0464d06f517@huawei.com> (raw)
In-Reply-To: <20190430161124.GM9224@smile.fi.intel.com>


在 2019/5/1 0:11, Andy Shevchenko 写道:
> On Tue, Apr 30, 2019 at 10:28:17AM +1000, Tobin C. Harding wrote:
>> Currently error return from kobject_init_and_add() is not followed by a
>> call to kobject_put().  This means there is a memory leak.
>>
>> Add call to kobject_put() in error path of kobject_init_and_add().
> It's not obvious to me if this will help to fix what is stated in the
> (reverted) commit 6b70fc94afd1 ("net-sysfs: Fix memory leak in
> netdev_register_kobject")?
>
> If so, perhaps we need to tell syzkaller guys about this.
Thanks for reminding. It seems that the bug has not been completely fixed.

in netdev_register_kobject():

1746         error = device_add(dev);
1747         if (error)
1748                 return error;
1749
1750         error = register_queue_kobjects(ndev);
1751         if (error) {
1752                 device_del(dev);
1753                 return error;
1754         }

This only fixes a memory leak after a failure in 
register_queue_kobjects(). If device_add() fails, kobject_put() still 
cann't be called, and the memory leak still exists.


      reply	other threads:[~2019-05-08 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30  0:28 [PATCH 0/3] " Tobin C. Harding
2019-04-30  0:28 ` [PATCH 1/3] bridge: " Tobin C. Harding
2019-04-30  1:23   ` Tobin C. Harding
2019-04-30  8:44   ` Greg Kroah-Hartman
2019-04-30 15:14   ` Tyler Hicks
2019-04-30 15:23     ` Tyler Hicks
2019-04-30 22:38   ` Tobin C. Harding
2019-04-30  0:28 ` [PATCH 2/3] bridge: Use correct cleanup function Tobin C. Harding
2019-04-30  8:44   ` Greg Kroah-Hartman
2019-04-30  0:28 ` [PATCH 3/3] net-sysfs: Fix error path for kobject_init_and_add() Tobin C. Harding
2019-04-30  8:45   ` Greg Kroah-Hartman
2019-04-30 15:37   ` Tyler Hicks
2019-04-30 16:11   ` Andy Shevchenko
2019-05-08 14:52     ` wanghai (M) [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=2062f0d4-e51f-106e-cd0b-f0464d06f517@huawei.com \
    --to=wanghai26@huawei.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=amritha.nambiar@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=idosch@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tobin@kernel.org \
    --cc=tyhicks@canonical.com \
    --cc=yuehaibing@huawei.com \
    --subject='Re: [PATCH 3/3] net-sysfs: Fix error path for kobject_init_and_add()' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).