All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: John Fastabend <john.fastabend@gmail.com>,
	Jakub Sitnicki <jakub@cloudflare.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	David Ahern <dsahern@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Mykola Lysenko <mykolal@fb.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
	 Mykyta Yatsenko <yatsenko@meta.com>, Miao Xu <miaxu@meta.com>,
	Yuran Pereira <yuran.pereira@hotmail.com>,
	Tiezhu Yang <yangtiezhu@loongson.cn>,
	Geliang Tang <tanggeliang@kylinos.cn>,
	 netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/4] Fixes for BPF selftests on Loongarch
Date: Tue, 25 Jun 2024 17:08:32 +0800	[thread overview]
Message-ID: <2319d0d58ccd879ebbc47f368475240bf06870ff.camel@kernel.org> (raw)
In-Reply-To: <CAAhV-H6=xEKDFS4f5hiOqw-gx1nKiXkQq8Kmr8ZsgQe9A3gbtw@mail.gmail.com>

On Tue, 2024-06-25 at 16:29 +0800, Huacai Chen wrote:
> On Tue, Jun 25, 2024 at 4:25 PM Geliang Tang <geliang@kernel.org>
> wrote:
> > 
> > From: Geliang Tang <tanggeliang@kylinos.cn>
> > 
> > v2:
> >  - add patch 2, a new fix for sk_msg_memcopy_from_iter.
> >  - update patch 3, only test "sk->sk_prot->close" as Eric
> > suggested.
> >  - update patch 4, use "goto err" instead of "return" as Eduard
> >    suggested.
> >  - add "fixes" tag for patch 1-3.
> >  - change subject prefixes as "bpf-next" to trigger BPF CI.
> >  - cc Loongarch maintainers too.
> > 
> > BPF selftests seem to have not been fully tested on Loongarch. When
> > I
> > ran these tests on Loongarch recently, some errors occur. This
> > patch set
> > contains some null-check related fixes for these errors.
> Is the root cause that LoongArch lacks bpf trampoline?

No. These errors don't seem to be directly related to the lack of BPF
trampoline. I have indeed got some errors since lacking BPF trampoline,
which is probably like this:

 test_dctcp:PASS:bpf_dctcp__open_and_load 0 nsec
 test_dctcp:FAIL:bpf_map__attach_struct_ops unexpected error: -524
 #29/1    bpf_tcp_ca/dctcp:FAIL
 test_cubic:PASS:bpf_cubic__open_and_load 0 nsec
 test_cubic:FAIL:bpf_map__attach_struct_ops unexpected error: -524
 #29/2    bpf_tcp_ca/cubic:FAIL
 test_dctcp_fallback:PASS:dctcp_skel 0 nsec
 test_dctcp_fallback:PASS:bpf_dctcp__load 0 nsec
 test_dctcp_fallback:FAIL:dctcp link unexpected error: -524
 #29/4    bpf_tcp_ca/dctcp_fallback:FAIL
 test_write_sk_pacing:PASS:open_and_load 0 nsec
 test_write_sk_pacing:FAIL:attach_struct_ops unexpected error: -524
 #29/6    bpf_tcp_ca/write_sk_pacing:FAIL

Thanks,
-Geliang

> 
> Huacai
> 
> > 
> > Geliang Tang (4):
> >   skmsg: null check for sg_page in sk_msg_recvmsg
> >   skmsg: null check for sg_page in sk_msg_memcopy_from_iter
> >   inet: null check for close in inet_release
> >   selftests/bpf: Null checks for link in bpf_tcp_ca
> > 
> >  net/core/skmsg.c                                 |  4 ++++
> >  net/ipv4/af_inet.c                               |  3 ++-
> >  .../selftests/bpf/prog_tests/bpf_tcp_ca.c        | 16
> > ++++++++++++----
> >  3 files changed, 18 insertions(+), 5 deletions(-)
> > 
> > --
> > 2.43.0
> > 


  reply	other threads:[~2024-06-25  9:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25  8:24 [PATCH bpf-next v2 0/4] Fixes for BPF selftests on Loongarch Geliang Tang
2024-06-25  8:24 ` [PATCH bpf-next v2 1/4] skmsg: null check for sg_page in sk_msg_recvmsg Geliang Tang
2024-06-25  8:33   ` Eric Dumazet
2024-06-25 19:37     ` John Fastabend
2024-06-26 13:05       ` Geliang Tang
2024-06-27  7:38         ` Geliang Tang
2024-06-25  8:24 ` [PATCH bpf-next v2 2/4] skmsg: null check for sg_page in sk_msg_memcopy_from_iter Geliang Tang
2024-06-25  8:24 ` [PATCH bpf-next v2 3/4] inet: null check for close in inet_release Geliang Tang
2024-06-25  8:31   ` Eric Dumazet
2024-06-25  8:24 ` [PATCH bpf-next v2 4/4] selftests/bpf: Null checks for link in bpf_tcp_ca Geliang Tang
2024-06-25  8:29 ` [PATCH bpf-next v2 0/4] Fixes for BPF selftests on Loongarch Huacai Chen
2024-06-25  9:08   ` Geliang Tang [this message]
2024-06-25  9:14     ` Huacai Chen

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=2319d0d58ccd879ebbc47f368475240bf06870ff.camel@kernel.org \
    --to=geliang@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=edumazet@google.com \
    --cc=haoluo@google.com \
    --cc=jakub@cloudflare.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=miaxu@meta.com \
    --cc=mykolal@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@google.com \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=tanggeliang@kylinos.cn \
    --cc=yangtiezhu@loongson.cn \
    --cc=yatsenko@meta.com \
    --cc=yonghong.song@linux.dev \
    --cc=yuran.pereira@hotmail.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 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.