From: bibo mao <maobibo@loongson.cn>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
loongarch@lists.linux.dev
Subject: Re: BUG: bpf test case fails to run on LoongArch
Date: Wed, 23 Apr 2025 09:49:13 +0800 [thread overview]
Message-ID: <c9d7be2b-8c2d-bd5e-b32d-37ed4bb693cc@loongson.cn> (raw)
In-Reply-To: <8cd87100-88f3-687d-6704-f4fec0ca48b3@loongson.cn>
On 2025/4/23 上午9:28, Tiezhu Yang wrote:
> On 04/21/2025 10:52 AM, bibo mao wrote:
>> Hi,
>>
>> When I run built-in bpf test case with lib/test_bpf.c,
>> it reports such error, I do not know whether it is a problem.
>>
>> test_bpf: #843 ALU32_RSH_X: all shift values jited:1 239 PASS
>> test_bpf: #844 ALU32_ARSH_X: all shift values jited:1 237 PASS
>> test_bpf: #845 ALU64_LSH_X: all shift values with the same register
>> ------------[ cut here ]------------
>> kernel BUG at lib/test_bpf.c:794!
>
> This is a known issue I have ever encountered.
> I guess your GCC version is 14.1, this is a bug of GCC,
yes, My gcc version is 14.1
> it has been fixed in the higher version, you can update
> you GCC version (14.2+).
OK, I will update my gcc. And sorry for the noise.
Regards
Bibo Mao
>
> $ gcc --version | head -1
> gcc (GCC) 14.2.1 20241104
> $ dmesg -t | grep Summary
> test_bpf: Summary: 1053 PASSED, 0 FAILED, [0/1041 JIT'ed]
> test_bpf: test_tail_calls: Summary: 10 PASSED, 0 FAILED, [0/10 JIT'ed]
> test_bpf: test_skb_segment: Summary: 2 PASSED, 0 FAILED
> test_bpf: Summary: 1053 PASSED, 0 FAILED, [1041/1041 JIT'ed]
> test_bpf: test_tail_calls: Summary: 10 PASSED, 0 FAILED, [10/10 JIT'ed]
> test_bpf: test_skb_segment: Summary: 2 PASSED, 0 FAILED
>
> Thanks,
> Tiezhu
>
prev parent reply other threads:[~2025-04-23 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 2:52 bibo mao
2025-04-23 1:28 ` Tiezhu Yang
2025-04-23 1:49 ` bibo mao [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=c9d7be2b-8c2d-bd5e-b32d-37ed4bb693cc@loongson.cn \
--to=maobibo@loongson.cn \
--cc=bpf@vger.kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=yangtiezhu@loongson.cn \
/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
all inboxes | Powered by JetHome®