Message ID | 20220920025123.2868953-3-liushixin2@huawei.com (mailing list archive) |
---|---|
State | New |
Headers | show |
Series | mm: Use hotplug_memory_notifier() instead of register_hotmemory_notifier() | expand |
On 20.09.22 04:51, Liu Shixin wrote: > Since patch 316346243be6 has already updated the minimum gcc version to 5.1. > The previous problem mentioned in patch f02c69680088 is not existed. So we > can now revert to use hotplug_memory_notifier() directly rather than > register_hotmemory_notifier(). > > Signed-off-by: Liu Shixin <liushixin2@huawei.com> > --- Reviewed-by: David Hildenbrand <david@redhat.com>
diff --git a/fs/proc/kcore.c b/fs/proc/kcore.c index dff921f7ca33..7692a360972d 100644 --- a/fs/proc/kcore.c +++ b/fs/proc/kcore.c @@ -18,7 +18,6 @@ #include <linux/capability.h> #include <linux/elf.h> #include <linux/elfcore.h> -#include <linux/notifier.h> #include <linux/vmalloc.h> #include <linux/highmem.h> #include <linux/printk.h> @@ -638,10 +637,6 @@ static int __meminit kcore_callback(struct notifier_block *self, return NOTIFY_OK; } -static struct notifier_block kcore_callback_nb __meminitdata = { - .notifier_call = kcore_callback, - .priority = 0, -}; static struct kcore_list kcore_vmalloc; @@ -694,7 +689,7 @@ static int __init proc_kcore_init(void) add_modules_range(); /* Store direct-map area from physical memory map */ kcore_update_ram(); - register_hotmemory_notifier(&kcore_callback_nb); + hotplug_memory_notifier(kcore_callback, 0); return 0; }
Since patch 316346243be6 has already updated the minimum gcc version to 5.1. The previous problem mentioned in patch f02c69680088 is not existed. So we can now revert to use hotplug_memory_notifier() directly rather than register_hotmemory_notifier(). Signed-off-by: Liu Shixin <liushixin2@huawei.com> --- fs/proc/kcore.c | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-)