All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: David Hildenbrand <david@redhat.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Alexander Potapenko <glider@google.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	"open list:KASAN" <kasan-dev@googlegroups.com>
Subject: Re: [PATCH v2 2/2] kasan: fix memory hotplug during boot
Date: Tue, 22 May 2018 14:07:35 -0700	[thread overview]
Message-ID: <20180522140735.71dcd92e7b013629a7f15f91@linux-foundation.org> (raw)
In-Reply-To: <09c36096-f8c8-b9e9-0bed-113e494f159a@virtuozzo.com>

On Tue, 22 May 2018 22:50:12 +0300 Andrey Ryabinin <aryabinin@virtuozzo.com> wrote:

> 
> 
> On 05/22/2018 07:36 PM, David Hildenbrand wrote:
> > On 22.05.2018 18:26, Andrey Ryabinin wrote:
> >>
> >>
> >> On 05/22/2018 01:07 PM, David Hildenbrand wrote:
> >>> 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.
> >>
> >>          reproducible
> >>>
> >>> Signed-off-by: David Hildenbrand <david@redhat.com>
> >>> ---
> >>
> >> Fixes: fa69b5989bb0 ("mm/kasan: add support for memory hotplug")
> >> Acked-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
> >> Cc: <stable@vger.kernel.org>
> > 
> > Think this even dates back to:
> > 
> > 786a8959912e ("kasan: disable memory hotplug")
> > 
> 
> Indeed.

Is a backport to -stable justified for either of these patches?

  reply	other threads:[~2018-05-22 21:07 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 ` [PATCH v2 2/2] kasan: fix memory hotplug during boot David Hildenbrand
2018-05-22 10:07   ` 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 [this message]
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=20180522140735.71dcd92e7b013629a7f15f91@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=david@redhat.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: 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.