All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wen Congyang <wency@cn.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	rientjes@google.com, liuj97@gmail.com, minchan.kim@gmail.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH 2/2]suppress "Device nodeX does not have a release() function" warning
Date: Wed, 17 Oct 2012 14:24:12 +0800	[thread overview]
Message-ID: <507E4F0C.9040506@cn.fujitsu.com> (raw)
In-Reply-To: <CAHGf_=rvdU+TymYZSXvx1bz4xdp43bqnyjRMGEoiBizC5rP0sQ@mail.gmail.com>

At 10/12/2012 06:33 AM, KOSAKI Motohiro Wrote:
> On Thu, Oct 11, 2012 at 1:26 AM, Yasuaki Ishimatsu
> <isimatu.yasuaki@jp.fujitsu.com> wrote:
>> When calling unregister_node(), the function shows following message at
>> device_release().
>>
>> "Device 'node2' does not have a release() function, it is broken and must
>> be fixed."
>>
>> The reason is node's device struct does not have a release() function.
>>
>> So the patch registers node_device_release() to the device's release()
>> function for suppressing the warning message. Additionally, the patch adds
>> memset() to initialize a node struct into register_node(). Because the node
>> struct is part of node_devices[] array and it cannot be freed by
>> node_device_release(). So if system reuses the node struct, it has a garbage.
>>
>> CC: David Rientjes <rientjes@google.com>
>> CC: Jiang Liu <liuj97@gmail.com>
>> Cc: Minchan Kim <minchan.kim@gmail.com>
>> CC: Andrew Morton <akpm@linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>> ---
>>  drivers/base/node.c |   11 +++++++++++
>>  1 file changed, 11 insertions(+)
>>
>> Index: linux-3.6/drivers/base/node.c
>> ===================================================================
>> --- linux-3.6.orig/drivers/base/node.c  2012-10-11 10:04:02.149758748 +0900
>> +++ linux-3.6/drivers/base/node.c       2012-10-11 10:20:34.111806931 +0900
>> @@ -252,6 +252,14 @@ static inline void hugetlb_register_node
>>  static inline void hugetlb_unregister_node(struct node *node) {}
>>  #endif
>>
>> +static void node_device_release(struct device *dev)
>> +{
>> +#if defined(CONFIG_MEMORY_HOTPLUG_SPARSE) && defined(CONFIG_HUGETLBFS)
>> +       struct node *node_dev = to_node(dev);
>> +
>> +       flush_work(&node_dev->node_work);
>> +#endif
>> +}
> 
> The patch description don't explain why this flush_work() is needed.

If the node is onlined after it is offlined, we will clear the memory,
so we should flush_work() before node_dev is set to 0.

Thanks
Wen Congyang

> 
> 
>>  /*
>>   * register_node - Setup a sysfs device for a node.
>> @@ -263,8 +271,11 @@ int register_node(struct node *node, int
>>  {
>>         int error;
>>
>> +       memset(node, 0, sizeof(*node));
>> +
> 
> You should add a comment why we need initialize a node here. A lot
> of developers don't have hotplug knowledge.
> 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Wen Congyang <wency@cn.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	rientjes@google.com, liuj97@gmail.com, minchan.kim@gmail.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH 2/2]suppress "Device nodeX does not have a release() function" warning
Date: Wed, 17 Oct 2012 14:24:12 +0800	[thread overview]
Message-ID: <507E4F0C.9040506@cn.fujitsu.com> (raw)
In-Reply-To: <CAHGf_=rvdU+TymYZSXvx1bz4xdp43bqnyjRMGEoiBizC5rP0sQ@mail.gmail.com>

At 10/12/2012 06:33 AM, KOSAKI Motohiro Wrote:
> On Thu, Oct 11, 2012 at 1:26 AM, Yasuaki Ishimatsu
> <isimatu.yasuaki@jp.fujitsu.com> wrote:
>> When calling unregister_node(), the function shows following message at
>> device_release().
>>
>> "Device 'node2' does not have a release() function, it is broken and must
>> be fixed."
>>
>> The reason is node's device struct does not have a release() function.
>>
>> So the patch registers node_device_release() to the device's release()
>> function for suppressing the warning message. Additionally, the patch adds
>> memset() to initialize a node struct into register_node(). Because the node
>> struct is part of node_devices[] array and it cannot be freed by
>> node_device_release(). So if system reuses the node struct, it has a garbage.
>>
>> CC: David Rientjes <rientjes@google.com>
>> CC: Jiang Liu <liuj97@gmail.com>
>> Cc: Minchan Kim <minchan.kim@gmail.com>
>> CC: Andrew Morton <akpm@linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>> ---
>>  drivers/base/node.c |   11 +++++++++++
>>  1 file changed, 11 insertions(+)
>>
>> Index: linux-3.6/drivers/base/node.c
>> ===================================================================
>> --- linux-3.6.orig/drivers/base/node.c  2012-10-11 10:04:02.149758748 +0900
>> +++ linux-3.6/drivers/base/node.c       2012-10-11 10:20:34.111806931 +0900
>> @@ -252,6 +252,14 @@ static inline void hugetlb_register_node
>>  static inline void hugetlb_unregister_node(struct node *node) {}
>>  #endif
>>
>> +static void node_device_release(struct device *dev)
>> +{
>> +#if defined(CONFIG_MEMORY_HOTPLUG_SPARSE) && defined(CONFIG_HUGETLBFS)
>> +       struct node *node_dev = to_node(dev);
>> +
>> +       flush_work(&node_dev->node_work);
>> +#endif
>> +}
> 
> The patch description don't explain why this flush_work() is needed.

If the node is onlined after it is offlined, we will clear the memory,
so we should flush_work() before node_dev is set to 0.

Thanks
Wen Congyang

> 
> 
>>  /*
>>   * register_node - Setup a sysfs device for a node.
>> @@ -263,8 +271,11 @@ int register_node(struct node *node, int
>>  {
>>         int error;
>>
>> +       memset(node, 0, sizeof(*node));
>> +
> 
> You should add a comment why we need initialize a node here. A lot
> of developers don't have hotplug knowledge.
> 


  reply	other threads:[~2012-10-17  6:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11  5:19 [PATCH v2 0/2] Suppress "Device <device name> does not have a release() function" warning Yasuaki Ishimatsu
2012-10-11  5:19 ` Yasuaki Ishimatsu
2012-10-11  5:22 ` [PATCH 1/2]suppress "Device memoryX " Yasuaki Ishimatsu
2012-10-11  5:22   ` Yasuaki Ishimatsu
2012-10-11 20:23   ` David Rientjes
2012-10-11 20:23     ` David Rientjes
2012-10-11 22:30   ` KOSAKI Motohiro
2012-10-11 22:30     ` KOSAKI Motohiro
2012-10-11  5:26 ` [PATCH 2/2]suppress "Device nodeX " Yasuaki Ishimatsu
2012-10-11  5:26   ` Yasuaki Ishimatsu
2012-10-11 20:31   ` David Rientjes
2012-10-11 20:31     ` David Rientjes
2012-10-12  0:13     ` Yasuaki Ishimatsu
2012-10-12  0:13       ` Yasuaki Ishimatsu
2012-10-11 22:33   ` KOSAKI Motohiro
2012-10-11 22:33     ` KOSAKI Motohiro
2012-10-17  6:24     ` Wen Congyang [this message]
2012-10-17  6:24       ` Wen Congyang
2012-10-17  8:50       ` KOSAKI Motohiro
2012-10-17  8:50         ` KOSAKI Motohiro
2012-10-19  5:42         ` Wen Congyang
2012-10-19  5:42           ` Wen Congyang

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=507E4F0C.9040506@cn.fujitsu.com \
    --to=wency@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuj97@gmail.com \
    --cc=minchan.kim@gmail.com \
    --cc=rientjes@google.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 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.