From: Eric Dumazet <eric.dumazet@gmail.com>
To: Wang Hai <wanghai26@huawei.com>,
davem@davemloft.net, idosch@mellanox.com, eric.dumazet@gmail.com,
alexander.h.duyck@intel.com, tyhicks@canonical.com,
f.fainelli@gmail.com, viro@zeniv.linux.org.uk,
amritha.nambiar@intel.com, joe@perches.com,
dmitry.torokhov@gmail.com, andriy.shevchenko@linux.intel.com,
stephen@networkplumber.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] net-sysfs: Fix memory leak in netdev_register_kobject
Date: Fri, 12 Apr 2019 06:03:27 -0700 [thread overview]
Message-ID: <855b85ea-5af9-9acd-1dbc-17b73703311c@gmail.com> (raw)
In-Reply-To: <20190412203634.30392-3-wanghai26@huawei.com>
On 04/12/2019 01:36 PM, Wang Hai wrote:
> When registering struct net_device, it will call
> register_netdevice ->
> netdev_register_kobject ->
> device_initialize(dev);
> dev_set_name(dev, "%s", ndev->name)
> device_add(dev)
> register_queue_kobjects(ndev)
>
> In netdev_register_kobject(), if device_add(dev) or
> register_queue_kobjects(ndev) failed. Register_netdevice()
> will return error, causing netdev_freemem(ndev) to be
> called to free net_device, however put_device(&dev->dev)->..->
> kobject_cleanup() won't be called, resulting in a memory leak
> which is alloced by dev_set_name()
>
>
Having two patches with exact same title is rather confusing for bug trackers.
Instead of revert + another_patch, why not just send a cumulative fix ?
next prev parent reply other threads:[~2019-04-12 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 20:36 [PATCH 0/2] net-sysfs: revert wrong bugfix and re-fix Wang Hai
2019-04-12 20:36 ` [PATCH 1/2] Revert "net-sysfs: Fix memory leak in netdev_register_kobject" Wang Hai
2019-04-12 8:38 ` Andy Shevchenko
2019-04-15 20:10 ` David Miller
2019-04-12 20:36 ` [PATCH 2/2] net-sysfs: Fix memory leak in netdev_register_kobject Wang Hai
2019-04-12 8:38 ` Andy Shevchenko
2019-04-12 12:08 ` wanghai (M)
2019-04-12 12:50 ` Al Viro
2019-04-12 13:03 ` Eric Dumazet [this message]
2019-04-12 13:20 ` Andy Shevchenko
2019-04-12 13:33 ` wanghai (M)
2019-04-12 13:28 ` 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=855b85ea-5af9-9acd-1dbc-17b73703311c@gmail.com \
--to=eric.dumazet@gmail.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=idosch@mellanox.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tyhicks@canonical.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wanghai26@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).