From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: jwi@linux.vnet.ibm.com, ubraun@linux.vnet.ibm.com,
davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: iucv: Free memory obtained by kzalloc
Date: Wed, 28 Feb 2018 17:14:55 +0530 [thread overview]
Message-ID: <e4784c9b-380f-4dad-6883-b6350a9e0614@gmail.com> (raw)
In-Reply-To: <20180228113042.6a2f5177.cohuck@redhat.com>
On Wednesday 28 February 2018 04:00 PM, Cornelia Huck wrote:
> On Wed, 28 Feb 2018 15:24:16 +0530
> Arvind Yadav <arvind.yadav.cs@gmail.com> wrote:
>
>> Free memory, if afiucv_iucv_init is not successful and
>> removing a IUCV driver.
>>
>> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
>> ---
>> net/iucv/af_iucv.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/net/iucv/af_iucv.c b/net/iucv/af_iucv.c
>> index 1e8cc7b..eb0995a 100644
>> --- a/net/iucv/af_iucv.c
>> +++ b/net/iucv/af_iucv.c
>> @@ -2433,9 +2433,11 @@ static int afiucv_iucv_init(void)
>> af_iucv_dev->driver = &af_iucv_driver;
>> err = device_register(af_iucv_dev);
>> if (err)
>> - goto out_driver;
>> + goto out_iucv_dev;
>> return 0;
>>
>> +out_iucv_dev:
>> + kfree(af_iucv_dev);
>> out_driver:
>> driver_unregister(&af_iucv_driver);
>> out_iucv:
>> @@ -2496,6 +2498,7 @@ static void __exit afiucv_exit(void)
>> {
>> if (pr_iucv) {
>> device_unregister(af_iucv_dev);
>> + kfree(af_iucv_dev);
>> driver_unregister(&af_iucv_driver);
>> pr_iucv->iucv_unregister(&af_iucv_handler, 0);
>> symbol_put(iucv_if);
> No, you must not use kfree() after you called device_register() (even
> if it was not successful!) -- see the comment for device_register().
Yes, Your are right. First we need to call put_device() then kfree().
I will send updated patch.
~arvind
next prev parent reply other threads:[~2018-02-28 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 9:54 [PATCH] net: iucv: Free memory obtained by kzalloc Arvind Yadav
2018-02-28 10:30 ` Cornelia Huck
2018-02-28 11:44 ` Arvind Yadav [this message]
2018-02-28 11:56 ` Cornelia Huck
2018-02-28 12:09 ` Arvind Yadav
2018-02-28 12:17 ` Aw: " Lino Sanfilippo
2018-02-28 12:31 ` Cornelia Huck
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=e4784c9b-380f-4dad-6883-b6350a9e0614@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=cohuck@redhat.com \
--cc=davem@davemloft.net \
--cc=jwi@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ubraun@linux.vnet.ibm.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