From: Borislav Petkov <bp@alien8.de>
To: kexec@lists.infradead.org
Subject: [PATCH v2 0/2] x86/kexec: fix memory leak of elf header buffer
Date: Wed, 13 Apr 2022 10:32:38 +0200 [thread overview]
Message-ID: <YlaKpuRQfIZsyBtL@zn.tnic> (raw)
In-Reply-To: <YlY51XjPFN1vMvQV@MiWiFi-R3L-srv>
On Wed, Apr 13, 2022 at 10:47:49AM +0800, Baoquan He wrote:
> Since it's also MM related, so ping you and x86 maintainers to see who
> can help pick them.
I'd leave that decision to akpm. :-)
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Baoquan He <bhe@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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:32:38 +0200 [thread overview]
Message-ID: <YlaKpuRQfIZsyBtL@zn.tnic> (raw)
In-Reply-To: <YlY51XjPFN1vMvQV@MiWiFi-R3L-srv>
On Wed, Apr 13, 2022 at 10:47:49AM +0800, Baoquan He wrote:
> Since it's also MM related, so ping you and x86 maintainers to see who
> can help pick them.
I'd leave that decision to akpm. :-)
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-04-13 8:32 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
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 [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=YlaKpuRQfIZsyBtL@zn.tnic \
--to=bp@alien8.de \
--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.