From: Uladzislau Rezki <urezki@gmail.com>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmalloc: add alignment info in warning print as possible failure reason
Date: Thu, 2 Jul 2026 19:48:27 +0200 [thread overview]
Message-ID: <akaka3D3IC883O5t@pc636> (raw)
In-Reply-To: <20260702112610.21589-1-feng.tang@linux.alibaba.com>
On Thu, Jul 02, 2026 at 07:26:10PM +0800, Feng Tang wrote:
> When running 'fix_align_alloc_test' case of test_vmalloc module with
> command:
> insmod ./test_vmalloc.ko run_test_mask=64
>
> It will fail, which is the expected result, as the case increment
> the alignment parameter gradually to 64bit limit. And the dmesg has
> warning msg:
> "vmalloc_test/0: vmalloc error: size 4096, vm_struct allocation failed, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0"
>
> It doesn't give the alignment info, which is the real reason for the
> failure (not the 'size').
>
> Add alignment info to the warning print to give the necessary hint
> for possible failure reason, and the message will be:
> "vmalloc_test/0: vmalloc error: size 4096, align 0x800000000000, vm_struct allocation failed, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0"
>
> Signed-off-by: Feng Tang <feng.tang@linux.alibaba.com>
> ---
> mm/vmalloc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 1afca3568b9b..e066324dcc76 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -4045,8 +4045,8 @@ void *__vmalloc_node_range_noprof(unsigned long size, unsigned long align,
> if (!area) {
> bool nofail = gfp_mask & __GFP_NOFAIL;
> warn_alloc(gfp_mask, NULL,
> - "vmalloc error: size %lu, vm_struct allocation failed%s",
> - size, (nofail) ? ". Retrying." : "");
> + "vmalloc error: size %lu, align 0x%lx, vm_struct allocation failed%s",
> + size, align, (nofail) ? ". Retrying." : "");
> if (nofail) {
> schedule_timeout_uninterruptible(1);
> goto again;
> --
> 2.43.5
>
Do not see any issues with adding extra information on failure.
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
--
Uladzislau Rezki
prev parent reply other threads:[~2026-07-02 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 11:26 [PATCH] mm/vmalloc: add alignment info in warning print as possible failure reason Feng Tang
2026-07-02 17:48 ` Uladzislau Rezki [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=akaka3D3IC883O5t@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@linux.alibaba.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.