From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, osalvador@suse.de, mhocko@suse.com,
david@redhat.com, aneesh.kumar@linux.ibm.com,
yangyingliang@huawei.com, akpm@linux-foundation.org
Subject: [folded-merged] mm-memory_hotplug-embed-vmem_altmap-details-in-memory-block-fix.patch removed from -mm tree
Date: Mon, 21 Aug 2023 13:29:13 -0700 [thread overview]
Message-ID: <20230821202913.B37A7C433C7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/memory_hotplug: fix error return code in add_memory_resource()
has been removed from the -mm tree. Its filename was
mm-memory_hotplug-embed-vmem_altmap-details-in-memory-block-fix.patch
This patch was dropped because it was folded into mm-memory_hotplug-embed-vmem_altmap-details-in-memory-block.patch
------------------------------------------------------
From: Yang Yingliang <yangyingliang@huawei.com>
Subject: mm/memory_hotplug: fix error return code in add_memory_resource()
Date: Wed, 9 Aug 2023 16:15:52 +0800
Set error return code to -ENOMEM, when kmalloc() fails.
Link: https://lkml.kernel.org/r/20230809081552.1351184-1-yangyingliang@huawei.com
Fixes: ad3232df3e41 ("mm/memory_hotplug: embed vmem_altmap details in memory block")
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Oscar Salvador <osalvador@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memory_hotplug.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--- a/mm/memory_hotplug.c~mm-memory_hotplug-embed-vmem_altmap-details-in-memory-block-fix
+++ a/mm/memory_hotplug.c
@@ -1440,8 +1440,10 @@ int __ref add_memory_resource(int nid, s
if (mhp_supports_memmap_on_memory(size)) {
mhp_altmap.free = memory_block_memmap_on_memory_pages();
params.altmap = kmalloc(sizeof(struct vmem_altmap), GFP_KERNEL);
- if (!params.altmap)
+ if (!params.altmap) {
+ ret = -ENOMEM;
goto error;
+ }
memcpy(params.altmap, &mhp_altmap, sizeof(mhp_altmap));
}
_
Patches currently in -mm which might be from yangyingliang@huawei.com are
mm-memory_hotplug-embed-vmem_altmap-details-in-memory-block.patch
reply other threads:[~2023-08-21 20:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230821202913.B37A7C433C7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=yangyingliang@huawei.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.