From: Baoquan He <bhe@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
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: Wed, 13 Apr 2022 10:47:49 +0800 [thread overview]
Message-ID: <YlY51XjPFN1vMvQV@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220412192734.fcda8988d189c8e2e2830b03@linux-foundation.org>
On 04/12/22 at 07:27pm, Andrew Morton wrote:
> 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.
Thanks, Andrew.
Since it's also MM related, so ping you and x86 maintainers to see who
can help pick them.
next prev parent reply other threads:[~2022-04-13 2:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 11:32 Baoquan He
2022-02-23 11:32 ` [PATCH v2 1/2] " Baoquan He
2022-02-23 11:32 ` [PATCH v2 2/2] kexec_file: clean up arch_kexec_kernel_image_load Baoquan He
2022-03-31 11:32 ` [PATCH v2 0/2] x86/kexec: fix memory leak of elf header buffer Baoquan He
2022-04-13 2:27 ` Andrew Morton
2022-04-13 2:47 ` Baoquan He [this message]
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=YlY51XjPFN1vMvQV@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=x86@kernel.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