From: Greg KH <gregkh@linuxfoundation.org>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: linmiaohe@huawei.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] memblock: use kfree() to release kmalloced memblock regions" failed to apply to 5.15-stable tree
Date: Mon, 28 Feb 2022 11:55:50 +0100 [thread overview]
Message-ID: <YhyqNv3PgdY6T5Ip@kroah.com> (raw)
In-Reply-To: <YhyXGAK9Se/ohdh9@linux.ibm.com>
On Mon, Feb 28, 2022 at 11:34:16AM +0200, Mike Rapoport wrote:
> On Mon, Feb 28, 2022 at 09:58:43AM +0100, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.15-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
>
> This version applies to 5.15 and should apply to older version as well.
>
> >From d4895990ebea634715d2dcf54121c5ae5a6612bc Mon Sep 17 00:00:00 2001
> From: Miaohe Lin <linmiaohe@huawei.com>
> Date: Thu, 17 Feb 2022 22:53:27 +0800
> Subject: [PATCH] memblock: use kfree() to release kmalloced memblock regions
>
> memblock.{reserved,memory}.regions may be allocated using kmalloc() in
> memblock_double_array(). Use kfree() to release these kmalloced regions
> indicated by memblock_{reserved,memory}_in_slab.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> Fixes: 3010f876500f ("mm: discard memblock data later")
> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
> mm/memblock.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-02-28 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 8:58 FAILED: patch "[PATCH] memblock: use kfree() to release kmalloced memblock regions" failed to apply to 5.15-stable tree gregkh
2022-02-28 9:34 ` Mike Rapoport
2022-02-28 10:55 ` Greg KH [this message]
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=YhyqNv3PgdY6T5Ip@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linmiaohe@huawei.com \
--cc=rppt@linux.ibm.com \
--cc=stable@vger.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