linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <tobin@kernel.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: "Tobin C. Harding" <tobin@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tyler Hicks <tyhicks@canonical.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Ido Schimmel <idosch@mellanox.com>,
	Alexander Duyck <alexander.h.duyck@intel.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Wang Hai <wanghai26@huawei.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: [PATCH 0/3] Fix error path for kobject_init_and_add()
Date: Tue, 30 Apr 2019 10:28:14 +1000	[thread overview]
Message-ID: <20190430002817.10785-1-tobin@kernel.org> (raw)

Hi Dave,

There are a few places in net/ that are not correctly handling the error
path after calls to kobject_init_and_add().  This set fixes all of these
for net/

This corrects a memory leak if kobject_init() is not followed by a call
to kobject_put()

This set is part of an effort to check/fix all of these mem leaks across
the kernel tree.

For reference this is the behaviour that we are trying to achieve

void fn(void)
{
	int ret;

	ret = kobject_init_and_add(kobj, ktype, NULL, "foo");
	if (ret) {
		kobject_put(kobj);
		return ret;
	}

	ret = some_init_fn();
	if (ret)
		goto err;

	ret = some_other_init_fn();
	if (ret)
		goto other_err;

	kobject_uevent(kobj, KOBJ_ADD);
	return 0;

other_err:
	other_clean_up_fn();
err:
	kobject_del(kobj);
	return ret;
}


Testing: No testing done, built with config options

CONFIG_NET=y
CONFIG_SYSFS=y
CONFIG_BRIDGE=y


thanks,
Tobin.

Tobin C. Harding (3):
  bridge: Fix error path for kobject_init_and_add()
  bridge: Use correct cleanup function
  net-sysfs: Fix error path for kobject_init_and_add()

 net/bridge/br_if.c   | 6 ++++--
 net/core/net-sysfs.c | 8 ++++++--
 2 files changed, 10 insertions(+), 4 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-04-30  0:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30  0:28 Tobin C. Harding [this message]
2019-04-30  0:28 ` [PATCH 1/3] bridge: Fix error path for kobject_init_and_add() 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)

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=20190430002817.10785-1-tobin@kernel.org \
    --to=tobin@kernel.org \
    --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=tyhicks@canonical.com \
    --cc=wanghai26@huawei.com \
    --cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).