From: <yadong.qi@linux.alibaba.com>
To: "'Andrew Morton'" <akpm@linux-foundation.org>
Cc: <urezki@gmail.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <ying.huang@linux.alibaba.com>
Subject: RE: [PATCH] mm: vmalloc: BUG_ON if mapping size is not PAGE_SIZE aligned
Date: Thu, 9 Oct 2025 14:04:08 +0800 [thread overview]
Message-ID: <000d01dc38e2$86ab7460$94025d20$@linux.alibaba.com> (raw)
In-Reply-To: <20251008211714.5a8b9fbb57dbe454cd4a9c6d@linux-foundation.org>
> -----Original Message-----
> From: Andrew Morton <akpm@linux-foundation.org>
> Sent: 2025年10月9日 12:17
> To: Yadong Qi <yadong.qi@linux.alibaba.com>
> Cc: urezki@gmail.com; linux-mm@kvack.org; linux-kernel@vger.kernel.org;
> ying.huang@linux.alibaba.com
> Subject: Re: [PATCH] mm: vmalloc: BUG_ON if mapping size is not PAGE_SIZE
> aligned
>
> On Thu, 9 Oct 2025 11:59:43 +0800 Yadong Qi <yadong.qi@linux.alibaba.com>
> wrote:
>
> > In mm/vmalloc.c, the function vmap_pte_range() assumes that the
> > mapping size is aligned to PAGE_SIZE. If this assumption is
> > violated, the loop will become infinite because the termination
> > condition (`addr != end`) will never be met. This can lead to
> > overwriting other VA ranges and/or random pages physically follow
> > the page table.
> >
> > It's the caller's responsibility to ensure that the mapping size
> > is aligned to PAGE_SIZE. However, the memory corruption is hard
> > to root cause. To identify the programming error in the caller
> > easier, check whether the mapping size is PAGE_SIZE aligned with
> > BUG_ON().
> >
> > ..
> >
> > --- a/mm/vmalloc.c
> > +++ b/mm/vmalloc.c
> > @@ -100,6 +100,8 @@ static int vmap_pte_range(pmd_t *pmd, unsigned long
> addr, unsigned long end,
> > struct page *page;
> > unsigned long size = PAGE_SIZE;
> >
> > + BUG_ON(!PAGE_ALIGNED(end - addr));
> > +
> > pfn = phys_addr >> PAGE_SHIFT;
> > pte = pte_alloc_kernel_track(pmd, addr, mask);
> > if (!pte)
>
> We try to avoid adding BUG()s - deliberately crashing the kernel is
> pretty cruel to the user. It's far better to WARN and to continue in
> some fashion so the user can at least gather logs, etc.
>
> How about
>
> if (WARN_ON(!PAGE_ALIGNED(end - addr)))
> return -ENOMEM;
>
> ?
>
> (Or VM_WARN_ON)
Sure, I will send a new patch with WARN_ON.
Best Regard
Yadong
prev parent reply other threads:[~2025-10-09 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 3:59 Yadong Qi
2025-10-09 4:17 ` Andrew Morton
2025-10-09 5:54 ` Lance Yang
2025-10-09 6:04 ` yadong.qi [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='000d01dc38e2$86ab7460$94025d20$@linux.alibaba.com' \
--to=yadong.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=urezki@gmail.com \
--cc=ying.huang@linux.alibaba.com \
/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