From: Uladzislau Rezki <urezki@gmail.com>
To: Barry Song <baohua@kernel.org>, Wen Jiang <jiangwenxiaomi@gmail.com>
Cc: Wen Jiang <jiangwenxiaomi@gmail.com>,
akpm@linux-foundation.org, urezki@gmail.com, dev.jain@arm.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Wen Jiang <jiangwen6@xiaomi.com>
Subject: Re: [PATCH] mm/vmalloc: bail out early on invalid page_shift in __vmap_pages_range_noflush()
Date: Sat, 3 Oct 2026 16:55:45 +0200 [thread overview]
Message-ID: <asEXcVSK1XL-tIa3@pc636> (raw)
In-Reply-To: <CAGsJ_4xWAd=VHPdGhS2AHKag2WhFA=_3MSOPuyt3ksKH9ezQ7g@mail.gmail.com>
On Sat, Oct 03, 2026 at 06:02:37PM +0800, Barry Song wrote:
> On Sat, Oct 3, 2026 at 5:05 PM Wen Jiang <jiangwenxiaomi@gmail.com> wrote:
> >
> > __vmap_pages_range_noflush() currently only warns when page_shift is
> > smaller than PAGE_SHIFT, then continues with the invalid shift. Return
> > -EINVAL instead so the bogus argument is caught immediately.
> >
> > Suggested-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> > Signed-off-by: Wen Jiang <jiangwen6@xiaomi.com>
>
> I have checked this carefully and confirmed that this is a correct cleanup.
>
> However, when I applied your patch, I noticed that the author and
> Signed-off-by do not match.
>
> Author: Wen Jiang <jiangwenxiaomi@gmail.com>
> Date: Sat Oct 3 17:04:30 2026 +0800
>
> mm/vmalloc: bail out early on invalid page_shift in
> __vmap_pages_range_noflush()
> ...
> Signed-off-by: Wen Jiang <jiangwen6@xiaomi.com>
>
>
> So please send a v2 to fix this, and feel free to include:
>
> Reviewed-by: Barry Song <baohua@kernel.org>
>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
--
Uladzislau Rezki
next prev parent reply other threads:[~2026-10-03 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 9:04 [PATCH] mm/vmalloc: bail out early on invalid page_shift in __vmap_pages_range_noflush() Wen Jiang
2026-10-03 10:02 ` Barry Song
2026-10-03 14:55 ` Uladzislau Rezki [this message]
2026-10-04 6:34 ` Wen Jiang
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=asEXcVSK1XL-tIa3@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=dev.jain@arm.com \
--cc=jiangwen6@xiaomi.com \
--cc=jiangwenxiaomi@gmail.com \
--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 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.