From: David Hildenbrand <david@redhat.com> To: linux-mm@kvack.org Cc: linux-kernel@vger.kernel.org, David Hildenbrand <david@redhat.com>, Andrey Ryabinin <aryabinin@virtuozzo.com>, Alexander Potapenko <glider@google.com>, Dmitry Vyukov <dvyukov@google.com>, kasan-dev@googlegroups.com (open list:KASAN) Subject: [PATCH v2 2/2] kasan: fix memory hotplug during boot Date: Tue, 22 May 2018 12:07:56 +0200 [thread overview] Message-ID: <20180522100756.18478-3-david@redhat.com> (raw) In-Reply-To: <20180522100756.18478-1-david@redhat.com> Using module_init() is wrong. E.g. ACPI adds and onlines memory before our memory notifier gets registered. This makes sure that ACPI memory detected during boot up will not result in a kernel crash. Easily reproducable with QEMU, just specify a DIMM when starting up. Signed-off-by: David Hildenbrand <david@redhat.com> --- mm/kasan/kasan.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c index 53564229674b..a8b85706e2d6 100644 --- a/mm/kasan/kasan.c +++ b/mm/kasan/kasan.c @@ -892,5 +892,5 @@ static int __init kasan_memhotplug_init(void) return 0; } -module_init(kasan_memhotplug_init); +core_initcall(kasan_memhotplug_init); #endif -- 2.17.0
WARNING: multiple messages have this Message-ID (diff)
From: David Hildenbrand <david@redhat.com> To: linux-mm@kvack.org Cc: linux-kernel@vger.kernel.org, David Hildenbrand <david@redhat.com>, Andrey Ryabinin <aryabinin@virtuozzo.com>, Alexander Potapenko <glider@google.com>, Dmitry Vyukov <dvyukov@google.com>, "open list:KASAN" <kasan-dev@googlegroups.com> Subject: [PATCH v2 2/2] kasan: fix memory hotplug during boot Date: Tue, 22 May 2018 12:07:56 +0200 [thread overview] Message-ID: <20180522100756.18478-3-david@redhat.com> (raw) In-Reply-To: <20180522100756.18478-1-david@redhat.com> Using module_init() is wrong. E.g. ACPI adds and onlines memory before our memory notifier gets registered. This makes sure that ACPI memory detected during boot up will not result in a kernel crash. Easily reproducable with QEMU, just specify a DIMM when starting up. Signed-off-by: David Hildenbrand <david@redhat.com> --- mm/kasan/kasan.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c index 53564229674b..a8b85706e2d6 100644 --- a/mm/kasan/kasan.c +++ b/mm/kasan/kasan.c @@ -892,5 +892,5 @@ static int __init kasan_memhotplug_init(void) return 0; } -module_init(kasan_memhotplug_init); +core_initcall(kasan_memhotplug_init); #endif -- 2.17.0
next prev parent reply other threads:[~2018-05-22 10:14 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-22 10:07 [PATCH v2 0/2] kasan: fix memory notifier handling David Hildenbrand 2018-05-22 10:07 ` [PATCH v2 1/2] kasan: free allocated shadow memory on MEM_CANCEL_ONLINE David Hildenbrand 2018-05-22 10:07 ` David Hildenbrand 2018-05-22 16:26 ` Andrey Ryabinin 2018-05-22 10:07 ` David Hildenbrand [this message] 2018-05-22 10:07 ` [PATCH v2 2/2] kasan: fix memory hotplug during boot David Hildenbrand 2018-05-22 16:26 ` Andrey Ryabinin 2018-05-22 16:36 ` David Hildenbrand 2018-05-22 19:50 ` Andrey Ryabinin 2018-05-22 21:07 ` Andrew Morton 2018-05-23 9:59 ` Andrey Ryabinin 2018-05-23 11:52 ` David Hildenbrand
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=20180522100756.18478-3-david@redhat.com \ --to=david@redhat.com \ --cc=aryabinin@virtuozzo.com \ --cc=dvyukov@google.com \ --cc=glider@google.com \ --cc=kasan-dev@googlegroups.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ /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: linkBe 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.