From: David Hildenbrand <david@redhat.com>
To: Aneesh Kumar K V <aneesh.kumar@linux.ibm.com>,
linux-mm@kvack.org, akpm@linux-foundation.org
Cc: Wei Xu <weixugc@google.com>, Huang Ying <ying.huang@intel.com>,
Yang Shi <shy828301@gmail.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Tim C Chen <tim.c.chen@intel.com>,
Michal Hocko <mhocko@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hesham Almatary <hesham.almatary@huawei.com>,
Dave Hansen <dave.hansen@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Alistair Popple <apopple@nvidia.com>,
Dan Williams <dan.j.williams@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
jvgediya.oss@gmail.com, Bharata B Rao <bharata@amd.com>
Subject: Re: [PATCH] mm/demotion: Fix kernel error with memory hotplug
Date: Fri, 26 Aug 2022 11:53:57 +0200 [thread overview]
Message-ID: <204b7465-0d30-d305-64fb-60fe46ca1dba@redhat.com> (raw)
In-Reply-To: <5b0d911b-4cc2-f1ae-b33b-79aca6e3124c@linux.ibm.com>
On 25.08.22 14:53, Aneesh Kumar K V wrote:
> On 8/25/22 5:46 PM, David Hildenbrand wrote:
>> On 25.08.22 11:20, Aneesh Kumar K.V wrote:
>>> On memory hot unplug, the kernel removes the node memory type
>>> from the associated memory tier. Use list_del_init instead of
>>> list del such that the same memory type can be added back
>>> to a memory tier on hotplug.
>>>
>>> Without this, we get the below warning and return error on
>>> adding memory type to a new memory tier.
>>>
>>> [ 33.596095] ------------[ cut here ]------------
>>> [ 33.596099] WARNING: CPU: 3 PID: 667 at mm/memory-tiers.c:115 set_node_memory_tier+0xd6/0x2e0
>>> [ 33.596109] Modules linked in: kmem
>>>
>>> ...
>>>
>>> [ 33.596126] RIP: 0010:set_node_memory_tier+0xd6/0x2e0
>>>
>>> ....
>>> [ 33.596196] memtier_hotplug_callback+0x48/0x68
>>> [ 33.596204] blocking_notifier_call_chain+0x80/0xc0
>>> [ 33.596211] online_pages+0x25e/0x280
>>> [ 33.596218] memory_block_change_state+0x176/0x1f0
>>> [ 33.596225] memory_subsys_online+0x37/0x40
>>> [ 33.596230] online_store+0x9b/0x130
>>> [ 33.596236] kernfs_fop_write_iter+0x128/0x1b0
>>> [ 33.596242] vfs_write+0x24b/0x2c0
>>> [ 33.596249] ksys_write+0x74/0xe0
>>> [ 33.596254] do_syscall_64+0x43/0x90
>>> [ 33.596259] entry_SYSCALL_64_after_hwframe+0x63/0xcd
>>>
>>> Fixes: mm/demotion: Add hotplug callbacks to handle new numa node onlined
>>
>> Do we have a proper 12-digit commit id as well?
>>
>> Do we have to cc stable?
>>
>
> That patch is not yet merged upstream. It is in mm-unstable. I guess Andrew can fold the change
> into the original patch?
>
Please make that clearer next time somehow -- either via "[PATCH
mm-unstable]" or just by stating "Andrew, please squash this into XYZ".
I know, akpm headquarter tracks all pending patches, but for other
reviewers this really helps to figure out how urgent this is and where
this applies to (+ saves time).
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2022-08-26 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 9:20 Aneesh Kumar K.V
2022-08-25 12:16 ` David Hildenbrand
2022-08-25 12:53 ` Aneesh Kumar K V
2022-08-26 0:25 ` Huang, Ying
2022-08-26 3:04 ` Andrew Morton
2022-08-26 9:53 ` David Hildenbrand [this message]
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=204b7465-0d30-d305-64fb-60fe46ca1dba@redhat.com \
--to=david@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=apopple@nvidia.com \
--cc=bharata@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=hannes@cmpxchg.org \
--cc=hesham.almatary@huawei.com \
--cc=jvgediya.oss@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shy828301@gmail.com \
--cc=tim.c.chen@intel.com \
--cc=weixugc@google.com \
--cc=ying.huang@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