From: Andrew Morton <akpm@linux-foundation.org>
To: kexec@lists.infradead.org
Subject: [PATCH v2 0/2] x86/kexec: fix memory leak of elf header buffer
Date: Tue, 12 Apr 2022 19:27:34 -0700 [thread overview]
Message-ID: <20220412192734.fcda8988d189c8e2e2830b03@linux-foundation.org> (raw)
In-Reply-To: <YkWRQdp7TxV22ygO@MiWiFi-R3L-srv>
On Thu, 31 Mar 2022 19:32:17 +0800 Baoquan He <bhe@redhat.com> wrote:
> Hi Andrew,
>
> On 02/23/22 at 07:32pm, Baoquan He wrote:
> > The memory leak is reported by kmemleak detector, has been existing
> > for very long time. It casue much memory loss on large machine
> > with huge memory hotplug which will trigger kdump kernel reloading
> > many times, with kexec_file_load interface.
>
> Could you merge these two patches? Or should I ping x86 maintainers to
> take them?
Ah, sorry, I tend to fall asleep if there's "x86" in the subject.
Poking a sleeping Andrew is always the right thing to do. Shall look
at them.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Baoquan He <bhe@redhat.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, dyoung@redhat.com, linux-mm@kvack.org
Subject: Re: [PATCH v2 0/2] x86/kexec: fix memory leak of elf header buffer
Date: Tue, 12 Apr 2022 19:27:34 -0700 [thread overview]
Message-ID: <20220412192734.fcda8988d189c8e2e2830b03@linux-foundation.org> (raw)
In-Reply-To: <YkWRQdp7TxV22ygO@MiWiFi-R3L-srv>
On Thu, 31 Mar 2022 19:32:17 +0800 Baoquan He <bhe@redhat.com> wrote:
> Hi Andrew,
>
> On 02/23/22 at 07:32pm, Baoquan He wrote:
> > The memory leak is reported by kmemleak detector, has been existing
> > for very long time. It casue much memory loss on large machine
> > with huge memory hotplug which will trigger kdump kernel reloading
> > many times, with kexec_file_load interface.
>
> Could you merge these two patches? Or should I ping x86 maintainers to
> take them?
Ah, sorry, I tend to fall asleep if there's "x86" in the subject.
Poking a sleeping Andrew is always the right thing to do. Shall look
at them.
next prev parent reply other threads:[~2022-04-13 2:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 11:32 [PATCH v2 0/2] x86/kexec: fix memory leak of elf header buffer Baoquan He
2022-02-23 11:32 ` Baoquan He
2022-02-23 11:32 ` [PATCH v2 1/2] " Baoquan He
2022-02-23 11:32 ` Baoquan He
2022-02-23 11:32 ` [PATCH v2 2/2] kexec_file: clean up arch_kexec_kernel_image_load Baoquan He
2022-02-23 11:32 ` Baoquan He
2022-03-31 11:32 ` [PATCH v2 0/2] x86/kexec: fix memory leak of elf header buffer Baoquan He
2022-03-31 11:32 ` Baoquan He
2022-04-13 2:27 ` Andrew Morton [this message]
2022-04-13 2:27 ` Andrew Morton
2022-04-13 2:47 ` Baoquan He
2022-04-13 2:47 ` Baoquan He
2022-04-13 8:32 ` Borislav Petkov
2022-04-13 8:32 ` Borislav Petkov
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=20220412192734.fcda8988d189c8e2e2830b03@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kexec@lists.infradead.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.