From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <liam@infradead.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/memory: fix hugetlb_zap_begin() call in zap_vma_range_batched()
Date: Thu, 3 Sep 2026 17:06:00 -0700 [thread overview]
Message-ID: <20260904000602.24574-1-sj@kernel.org> (raw)
In-Reply-To: <20260904000028.149656-1-sj@kernel.org>
On Thu, 3 Sep 2026 17:00:26 -0700 SJ Park <sj@kernel.org> wrote:
> Commit f1fc44daf618 ("mm/hugetlb: don't lock private resv_map during
> final unmap")
FYI, this commit is in only mm-new.
> added zap_details parameter to hugetlb_zap_begin(). But
> the hugetlb_zap_begin() call in zap_vma_range_batched() is not updated.
> As a result, build fails as below. Fix it.
>
> CC mm/memory.o
> .../mm/memory.c: In function ‘zap_vma_range_batched’:
> .../mm/memory.c:2308:9: error: too few arguments to function ‘hugetlb_zap_begin’
> 2308 | hugetlb_zap_begin(vma, &range.start, &range.end);
> | ^~~~~~~~~~~~~~~~~
> In file included from .../mm/memory.c:48:
> .../include/linux/hugetlb.h:253:20: note: declared here
> 253 | static inline void hugetlb_zap_begin(struct vm_area_struct *vma,
> | ^~~~~~~~~~~~~~~~~
>
> /* TODO: move below to commentary */
Oops, somehow my tool didn't process this... Sorry for noise.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-09-04 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 0:00 [PATCH] mm/memory: fix hugetlb_zap_begin() call in zap_vma_range_batched() SJ Park
2026-09-04 0:06 ` SJ Park [this message]
2026-09-04 0:22 ` SJ Park
2026-09-04 0:35 ` Andrew Morton
2026-09-04 1:15 ` SJ Park
2026-09-07 17:05 ` Zenghui Yu
2026-09-08 0:14 ` Zi Yan
2026-09-09 3:01 ` Andrew Morton
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=20260904000602.24574-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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 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.