From: Yonghong Song <yhs@fb.com>
To: Song Liu <song@kernel.org>, bpf@vger.kernel.org, netdev@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kernel-team@fb.com, kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH bpf-next 1/2] x86: disable HAVE_ARCH_HUGE_VMALLOC on 32-bit x86
Date: Tue, 1 Mar 2022 23:08:36 -0800 [thread overview]
Message-ID: <a9a4e58c-44a1-8ca8-80a6-eec3c3980539@fb.com> (raw)
In-Reply-To: <20220302004339.3932356-2-song@kernel.org>
On 3/1/22 4:43 PM, Song Liu wrote:
> kernel test robot reported kernel BUG like:
>
> [ 44.587744][ T1] kernel BUG at arch/x86/mm/physaddr.c:76!
> [ 44.590151][ T1] __vmalloc_area_node (mm/vmalloc.c:622 mm/vmalloc.c:2995)
> [ 44.590151][ T1] __vmalloc_node_range (mm/vmalloc.c:3108)
> [ 44.590151][ T1] __vmalloc_node (mm/vmalloc.c:3157)
>
> which is triggered with HAVE_ARCH_HUGE_VMALLOC on 32-bit x86. Since BPF
> only uses HAVE_ARCH_HUGE_VMALLOC for x86_64, turn it off for 32-bit x86.
>
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Fixes: fac54e2bfb5b ("x86/Kconfig: Select HAVE_ARCH_HUGE_VMALLOC with HAVE_ARCH_HUGE_VMAP")
> Signed-off-by: Song Liu <song@kernel.org>
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2022-03-02 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 0:43 [PATCH bpf-next 0/2] fixes for bpf_prog_pack Song Liu
2022-03-02 0:43 ` [PATCH bpf-next 1/2] x86: disable HAVE_ARCH_HUGE_VMALLOC on 32-bit x86 Song Liu
2022-03-02 7:08 ` Yonghong Song [this message]
2022-03-02 0:43 ` [PATCH bpf-next 2/2] bpf, x86: set header->size properly before freeing it Song Liu
2022-03-02 7:12 ` Yonghong Song
2022-03-02 17:24 ` Song Liu
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=a9a4e58c-44a1-8ca8-80a6-eec3c3980539@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=song@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