From: Mike Rapoport <rppt@linux.ibm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"labbott@redhat.com" <labbott@redhat.com>,
"iamjoonsoo.kim@lge.com" <iamjoonsoo.kim@lge.com>,
"mhocko@suse.com" <mhocko@suse.com>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"rppt@linux.vnet.ibm.com" <rppt@linux.vnet.ibm.com>,
"m.szyprowski@samsung.com" <m.szyprowski@samsung.com>,
"andreyknvl@google.com" <andreyknvl@google.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"van.freenix@gmail.com" <van.freenix@gmail.com>
Subject: Re: [PATCH V2] mm/cma: cma_declare_contiguous: correct err handling
Date: Wed, 27 Feb 2019 17:36:26 +0200 [thread overview]
Message-ID: <20190227153626.GF16901@rapoport-lnx> (raw)
In-Reply-To: <20190227144631.16708-1-peng.fan@nxp.com>
On Wed, Feb 27, 2019 at 02:34:55PM +0000, Peng Fan wrote:
> In case cma_init_reserved_mem failed, need to free the memblock allocated
> by memblock_reserve or memblock_alloc_range.
>
> Quote Catalin's comments:
> https://lkml.org/lkml/2019/2/26/482
> Kmemleak is supposed to work with the memblock_{alloc,free} pair and it
> ignores the memblock_reserve() as a memblock_alloc() implementation
> detail. It is, however, tolerant to memblock_free() being called on
> a sub-range or just a different range from a previous memblock_alloc().
> So the original patch looks fine to me. FWIW:
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
>
> V2:
> Per Mike's comments, add more information in commit log
> Add R-B
>
> mm/cma.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/mm/cma.c b/mm/cma.c
> index c7b39dd3b4f6..f4f3a8a57d86 100644
> --- a/mm/cma.c
> +++ b/mm/cma.c
> @@ -353,12 +353,14 @@ int __init cma_declare_contiguous(phys_addr_t base,
>
> ret = cma_init_reserved_mem(base, size, order_per_bit, name, res_cma);
> if (ret)
> - goto err;
> + goto free_mem;
>
> pr_info("Reserved %ld MiB at %pa\n", (unsigned long)size / SZ_1M,
> &base);
> return 0;
>
> +free_mem:
> + memblock_free(base, size);
> err:
> pr_err("Failed to reserve %ld MiB\n", (unsigned long)size / SZ_1M);
> return ret;
> --
> 2.16.4
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2019-02-27 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 14:34 [PATCH V2] mm/cma: cma_declare_contiguous: correct err handling Peng Fan
2019-02-27 15:36 ` Mike Rapoport [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=20190227153626.GF16901@rapoport-lnx \
--to=rppt@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=catalin.marinas@arm.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mhocko@suse.com \
--cc=peng.fan@nxp.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=van.freenix@gmail.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).