From: wangyufen <wangyufen@huawei.com>
To: Martin KaFai Lau <martin.lau@linux.dev>,
Lina Wang <lina.wang@mediatek.com>
Cc: <bpf@vger.kernel.org>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<deso@posteo.net>, <netdev@vger.kernel.org>
Subject: Re: [net 1/2] selftests/net: fix opening object file failed
Date: Tue, 18 Oct 2022 17:50:19 +0800 [thread overview]
Message-ID: <793d2d69-cf52-defc-6964-8b7c95bb45c4@huawei.com> (raw)
In-Reply-To: <b38c7c5e-bd88-0257-42f4-773d8791330a@huawei.com>
在 2022/10/18 10:57, wangyufen 写道:
>
> 在 2022/10/13 9:51, Martin KaFai Lau 写道:
>> On 10/11/22 2:57 AM, Wang Yufen wrote:
>>> The program file used in the udpgro_frglist testcase is
>>> "../bpf/nat6to4.o",
>>> but the actual nat6to4.o file is in "bpf/" not "../bpf".
>>> The following error occurs:
>>> Error opening object ../bpf/nat6to4.o: No such file or directory
>>
>> hmm... so it sounds like the test never works...
>>
>> The test seems like mostly exercising the tc-bpf? It makes sense to
>> move it to the selftests/bpf. or staying in net is also fine for now
>> and only need to fix up the path here.
>>
>> However, if moving to selftests/bpf, I don't think it is a good idea
>> to only move the bpf prog but not moving the actual test program (the
>> script here) such that the bpf CI can continuously testing it.
>> Otherwise, it will just drift and rot slowly like patch 2.
>>
>> Also, if you prefer to move it to selftests/bpf, the bpf prog cannot
>> be moved in the current form. eg. There is some convention on the
>> SEC name in the selftests/bpf/progs. Also, the testing script needs
>> to be adapted to the selftests/bpf/test_progs infra.
>
> hmm... if moving to selftests/bpf, the actual test programs also needs
> to move to selftests/bpf, e.g. udpgso_bench_*, in_netns.sh,
> udpgso*.sh, which may not be a good idea.
>
> So, only fix up the path here.
>
> Also fix up the bpf/nat6to4.o compile error as following:
>
> make -C tools/testing/selftests/net got the following err:
> bpf/nat6to4.c:43:10: fatal error: 'bpf/bpf_helpers.h' file not found
> ^~~~~~~~~~~~~~~~~~~
>
>
After revert commit 7b92aa9e61350("selftests net: fix kselftest net
fatal error"),
make -C tools/testing/selftests got the following err:
In file included from bpf/nat6to4.c:43:
../../../lib/bpf/bpf_helpers.h:11:10: fatal error: 'bpf_helper_defs.h'
file not found
#include "bpf_helper_defs.h"
^~~~~~~~~~~~~~~~~~~
"bpf_helper_defs.h" is generated by libbpf;
So, there are two possible approaches: the first moving nat6to4.c and
the actual test programs to selftests/bpf;
second add make dependency on libbpf for the nat6to4.c.
Which one is better?
next prev parent reply other threads:[~2022-10-18 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 9:57 [net 0/2] some fixes for selftest/net Wang Yufen
2022-10-11 9:57 ` [net 1/2] selftests/net: fix opening object file failed Wang Yufen
2022-10-13 1:51 ` Martin KaFai Lau
2022-10-18 2:57 ` wangyufen
2022-10-18 9:50 ` wangyufen [this message]
2022-10-18 16:26 ` Alexei Starovoitov
2022-10-18 18:00 ` Jakub Kicinski
2022-10-19 1:30 ` Martin KaFai Lau
2022-10-19 1:53 ` Jakub Kicinski
2022-10-11 9:57 ` [net 2/2] selftests/net: fix missing xdp_dummy Wang Yufen
2022-10-11 16:27 ` Daniel Müller
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=793d2d69-cf52-defc-6964-8b7c95bb45c4@huawei.com \
--to=wangyufen@huawei.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=deso@posteo.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lina.wang@mediatek.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).