linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: CharSyam <charsyam@gmail.com>
To: Donet Tom <donettom@linux.ibm.com>
Cc: Mike Rapoport <rppt@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Masami Hiramatsu <mhiramat@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	stable@vger.kernel.org,  linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/memblock: fix off-by-one page leak in reserve_mem_release_by_name()
Date: Tue, 14 Apr 2026 20:20:42 +0900	[thread overview]
Message-ID: <CAMrLSE7CAJ-eqxhijGJUw07_7Z8a7q7jpOi9+VE_4Uu3NovqZA@mail.gmail.com> (raw)
In-Reply-To: <b1a5b96a-a525-4566-876d-5286c1367d7a@linux.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]

  Please disregard this patch -- I just noticed the same fix is already
  in linux-next as commit c12c3e150780 ("memblock: reserve_mem: fix end
  caclulation in reserve_mem_release_by_name()") by Mike Rapoport.

  Sorry for the noise.

  Thanks,
  DaeMyung

2026년 4월 14일 (화) 오후 8:13, Donet Tom <donettom@linux.ibm.com>님이 작성:

> Hi
>
> On 4/14/26 4:13 PM, DaeMyung Kang wrote:
> > free_reserved_area() treats its 'end' argument as exclusive: it aligns
> > end down via 'end & PAGE_MASK' and iterates with 'pos < end'.
> >
> > reserve_mem_release_by_name() instead passes 'start + map->size - 1',
> > which causes the last page of a page-aligned reservation to never be
> > freed. For a reservation spanning N pages, only N - 1 pages are
> > released back to the allocator.
> >
> > Fix it by passing the exclusive end address, 'start + map->size'.
> >
> > Fixes: 74e2498ccf7b ("mm/memblock: Add reserved memory release function")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: DaeMyung Kang <charsyam@gmail.com>
>
>
> I think it might be better to send v2 as a separate patch  rather than
> as a reply to the previous version.
>
> This patch looks good to me.
>
> Reviewed-by: Donet Tom donettom@linux.ibm.com
>
> -Donet
>
>
> > ---
> > Changes in v2:
> >   - Add Fixes: tag and Cc: stable (per Donet Tom's review).
> >   - v1: https://lore.kernel.org/lkml/
> >
> >   mm/memblock.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/mm/memblock.c b/mm/memblock.c
> > index b3ddfdec7a80..d4a02f1750e9 100644
> > --- a/mm/memblock.c
> > +++ b/mm/memblock.c
> > @@ -2434,7 +2434,7 @@ int reserve_mem_release_by_name(const char *name)
> >               return 0;
> >
> >       start = phys_to_virt(map->start);
> > -     end = start + map->size - 1;
> > +     end = start + map->size;
> >       snprintf(buf, sizeof(buf), "reserve_mem:%s", name);
> >       free_reserved_area(start, end, 0, buf);
> >       map->size = 0;
>

[-- Attachment #2: Type: text/html, Size: 2980 bytes --]

  reply	other threads:[~2026-04-14 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14  9:44 [PATCH] " DaeMyung Kang
2026-04-14 10:10 ` Donet Tom
2026-04-14 10:43 ` [PATCH v2] " DaeMyung Kang
2026-04-14 11:13   ` Donet Tom
2026-04-14 11:20     ` CharSyam [this message]
     [not found] <V1-MESSAGE-ID>
2026-04-14 10:42 ` DaeMyung Kang

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=CAMrLSE7CAJ-eqxhijGJUw07_7Z8a7q7jpOi9+VE_4Uu3NovqZA@mail.gmail.com \
    --to=charsyam@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=donettom@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=rppt@kernel.org \
    --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