All of lore.kernel.org
 help / color / mirror / Atom feed
From: arvindY <arvind.yadav.cs@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: memory_hotplug: use put_device() if device_register fail
Date: Sat, 28 Apr 2018 11:05:44 +0530	[thread overview]
Message-ID: <5AE40830.2090007@gmail.com> (raw)
In-Reply-To: <20180427145623.GC5404@dhcp22.suse.cz>



On Friday 27 April 2018 08:26 PM, Michal Hocko wrote:
> On Thu 26-04-18 21:12:09, Arvind Yadav wrote:
>> if device_register() returned an error. Always use put_device()
>> to give up the initialized reference and release allocated memory.
> Is this patch correct? The docummentation says
>   * NOTE: _Never_ directly free @dev after calling this function, even
>   * if it returned an error! Always use put_device() to give up your
>   * reference instead.
>
> but we do not have _our_ reference in this path AFAICS. Maybe this is
> just a documentation issue? How have you tested this change btw.?
The document is correct. Here device_register() will initialize object by
making reference count as 1 and also increment reference count for device.

device_register() {
    device_initialize()->kobject_init()->kref_init() - initialize 
object( reference count = 1).
    device_add()->get_device() - increment reference count for device.
}

If device_register() will fail then we have to release the object by making
reference count 0. So we need to call put_object() which will release the
object and other resources like memory etc. so long as the reference
count is nonzero, the object continue to exist in memory.

I have not tested this peace of code. But I have tested other code which
is using Kboject.

~arvind
>
>> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
>> ---
>>   drivers/base/memory.c | 8 +++++++-
>>   1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
>> index bffe861..f5e5601 100644
>> --- a/drivers/base/memory.c
>> +++ b/drivers/base/memory.c
>> @@ -649,13 +649,19 @@ static const struct attribute_group *memory_memblk_attr_groups[] = {
>>   static
>>   int register_memory(struct memory_block *memory)
>>   {
>> +	int ret;
>> +
>>   	memory->dev.bus = &memory_subsys;
>>   	memory->dev.id = memory->start_section_nr / sections_per_block;
>>   	memory->dev.release = memory_block_release;
>>   	memory->dev.groups = memory_memblk_attr_groups;
>>   	memory->dev.offline = memory->state == MEM_OFFLINE;
>>   
>> -	return device_register(&memory->dev);
>> +	ret = device_register(&memory->dev);
>> +	if (ret)
>> +		put_device(&memory->dev);
>> +
>> +	return ret;
>>   }
>>   
>>   static int init_memory_block(struct memory_block **memory,
>> -- 
>> 2.7.4

  reply	other threads:[~2018-04-28  5:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 15:42 [PATCH] mm: memory_hotplug: use put_device() if device_register fail Arvind Yadav
2018-04-27 14:56 ` Michal Hocko
2018-04-28  5:35   ` arvindY [this message]
2018-05-02 14:27     ` Michal Hocko

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=5AE40830.2090007@gmail.com \
    --to=arvind.yadav.cs@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@kernel.org \
    /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.