From: David Hildenbrand <david@redhat.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
"open list:KASAN" <kasan-dev@googlegroups.com>
Subject: Re: [PATCH v1 1/2] kasan: free allocated shadow memory on MEM_CANCEL_OFFLINE
Date: Tue, 22 May 2018 11:58:13 +0200 [thread overview]
Message-ID: <781aad97-3fe7-cf78-ad27-464254a5da27@redhat.com> (raw)
In-Reply-To: <20180522095515.2735-2-david@redhat.com>
On 22.05.2018 11:55, David Hildenbrand wrote:
> We have to free memory again when we cancel onlining, otherwise a later
> onlining attempt will fail.
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> mm/kasan/kasan.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c
> index 135ce2838c89..8baefe1a674b 100644
> --- a/mm/kasan/kasan.c
> +++ b/mm/kasan/kasan.c
> @@ -867,6 +867,7 @@ static int __meminit kasan_mem_notifier(struct notifier_block *nb,
> kmemleak_ignore(ret);
> return NOTIFY_OK;
> }
> + case MEM_CANCEL_OFFLINE:
Typo, MEM_CANCEL_ONLINE
> case MEM_OFFLINE: {
> struct vm_struct *vm;
>
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2018-05-22 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 9:55 [PATCH v1 0/2] kasan: fix memory notifier handling David Hildenbrand
2018-05-22 9:55 ` [PATCH v1 1/2] kasan: free allocated shadow memory on MEM_CANCEL_OFFLINE David Hildenbrand
2018-05-22 9:58 ` David Hildenbrand [this message]
2018-05-22 9:55 ` [PATCH v1 2/2] kasan: fix memory hotplug during boot 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=781aad97-3fe7-cf78-ad27-464254a5da27@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: 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