linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Ercan Ersoy <ercanersoy@ercanersoy.net>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, akpm@linux-foundation.org
Subject: Re: [PATCH 2/2] Fix assgining cma_area_count
Date: Wed, 12 Jan 2022 10:22:01 +0100	[thread overview]
Message-ID: <4cbe2f51-0654-dcfa-cd9c-1b5096cc5394@redhat.com> (raw)
In-Reply-To: <775ae3ba4f7034a78769559fa1a3542a@ercanersoy.net>

On 09.01.22 08:39, Ercan Ersoy wrote:
> 
> I have patched "Contiguous Memory Allocator" of Linux kernel.
> 
> This fix of patch is for cma_init_reserved_mem function in
> mm/cma.c source file as creating area without specific name.
> 
> Without fix may be a problem a lot of cma as next cma2147483647 naming.
> Without fix may be a problem huge memory systems.
> 
> I think after "cma2147483647" naming is "cma-2147483648".
> 
> Thanks for interesting,
> Ercan
> 
> --- START PATCH ---
>  From 5d3d01a3a0f7339617d1df945c0bd0ec1ab91ae3 Mon Sep 17 00:00:00 2001
>  From: Ercan Ersoy <ercanersoy@ercanersoy.net>
> Date: Sun, 9 Jan 2022 10:01:14 +0300
> Subject: [PATCH 2/2] Fix assgining cma_area_count
> 
> Fix assigning to cma->name in cma_init_reserved_mem function
> in mm/cma.c source file.
> 

Honestly, how on earth are we supposed to have that many CMA areas?

It's limited by MAX_CMA_AREAS, which is usually ... 7 or 19.

Calling this a fix is a bit though. This is a cleanup we might not care
too much about.

> Signed-off-by: Ercan Ersoy <ercanersoy@ercanersoy.net>
> ---
>   mm/cma.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/mm/cma.c b/mm/cma.c
> index bc9ca8f3c487..03f01d1f1b57 100644
> --- a/mm/cma.c
> +++ b/mm/cma.c
> @@ -199,7 +199,7 @@ int __init cma_init_reserved_mem(phys_addr_t base, 
> phys_addr_t size,
>   	if (name)
>   		snprintf(cma->name, CMA_MAX_NAME, name);
>   	else
> -		snprintf(cma->name, CMA_MAX_NAME,  "cma%d\n", cma_area_count);
> +		snprintf(cma->name, CMA_MAX_NAME,  "cma%u\n", cma_area_count);
> 
>   	cma->base_pfn = PFN_DOWN(base);
>   	cma->count = size >> PAGE_SHIFT;


-- 
Thanks,

David / dhildenb



      reply	other threads:[~2022-01-12  9:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09  7:39 Ercan Ersoy
2022-01-12  9:22 ` David Hildenbrand [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=4cbe2f51-0654-dcfa-cd9c-1b5096cc5394@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ercanersoy@ercanersoy.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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