linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Dufour <ldufour@linux.ibm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: akpm@linux-foundation.org, David Hildenbrand <david@redhat.com>,
	Oscar Salvador <osalvador@suse.de>,
	mhocko@kernel.org, linux-mm@kvack.org,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	nathanl@linux.ibm.com, cheloha@linux.ibm.com,
	Tony Luck <tony.luck@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mm: don't panic when links can't be created in sysfs
Date: Fri, 11 Sep 2020 18:27:41 +0200	[thread overview]
Message-ID: <3713153c-d239-e6f9-fc1a-a3e4357ee069@linux.ibm.com> (raw)
In-Reply-To: <20200911140100.GA3812164@kroah.com>

Le 11/09/2020 à 16:01, Greg Kroah-Hartman a écrit :
> On Fri, Sep 11, 2020 at 03:48:31PM +0200, Laurent Dufour wrote:
>> At boot time, or when doing memory hot-add operations, if the links in
>> sysfs can't be created, the system is still able to run, so just report the
>> error in the kernel log.
>>
>> Since the number of memory blocks managed could be high, the messages are
>> rate limited.
>>
>> As a consequence, link_mem_sections() has no status to report anymore.
>>
>> Signed-off-by: Laurent Dufour <ldufour@linux.ibm.com>
>> Cc: David Hildenbrand <david@redhat.com>
>> ---
>>   drivers/base/node.c  | 25 +++++++++++++++++--------
>>   include/linux/node.h | 17 ++++++++---------
>>   mm/memory_hotplug.c  |  5 ++---
>>   3 files changed, 27 insertions(+), 20 deletions(-)
>>
>> diff --git a/drivers/base/node.c b/drivers/base/node.c
>> index 862516c5a5ae..749a1c8ea992 100644
>> --- a/drivers/base/node.c
>> +++ b/drivers/base/node.c
>> @@ -811,12 +811,21 @@ static int register_mem_sect_under_node(struct memory_block *mem_blk,
>>   		ret = sysfs_create_link_nowarn(&node_devices[nid]->dev.kobj,
>>   					&mem_blk->dev.kobj,
>>   					kobject_name(&mem_blk->dev.kobj));
>> -		if (ret)
>> -			return ret;
>> +		if (ret && ret != -EEXIST)
>> +			pr_err_ratelimited(
>> +				"can't create %s to %s link in sysfs (%d)\n",
>> +				kobject_name(&node_devices[nid]->dev.kobj),
>> +				kobject_name(&mem_blk->dev.kobj), ret);
> 
> dev_err_ratelimited()?

Thanks Greg, I was not aware about this.

> Same elsewhere in this patch.
> 
> thanks,
> 
> greg k-h
> 



  reply	other threads:[~2020-09-11 16:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 13:48 mm: fix memory to node bad links " Laurent Dufour
2020-09-11 13:48 ` [PATCH 1/3] mm: replace memmap_context by memplug_context Laurent Dufour
2020-09-11 14:59   ` David Hildenbrand
2020-09-11 16:23     ` Laurent Dufour
2020-09-11 17:34       ` David Hildenbrand
2020-09-14  8:49   ` Michal Hocko
2020-09-14  8:51     ` Laurent Dufour
2020-09-14  8:59       ` Michal Hocko
2020-09-11 13:48 ` [PATCH 2/3] mm: don't rely on system state to detect hot-plug operations Laurent Dufour
2020-09-14  7:57   ` David Hildenbrand
2020-09-14  8:05     ` Laurent Dufour
2020-09-14  8:19     ` Oscar Salvador
2020-09-14  8:31       ` David Hildenbrand
2020-09-14  9:16         ` Laurent Dufour
2020-09-14  9:19           ` David Hildenbrand
2020-09-14  8:39       ` Laurent Dufour
2020-09-14  8:55   ` Michal Hocko
2020-09-11 13:48 ` [PATCH 3/3] mm: don't panic when links can't be created in sysfs Laurent Dufour
2020-09-11 14:01   ` Greg Kroah-Hartman
2020-09-11 16:27     ` Laurent Dufour [this message]
2020-09-14  8:59   ` 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=3713153c-d239-e6f9-fc1a-a3e4357ee069@linux.ibm.com \
    --to=ldufour@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=cheloha@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=fenghua.yu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=nathanl@linux.ibm.com \
    --cc=osalvador@suse.de \
    --cc=rafael@kernel.org \
    --cc=tony.luck@intel.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