From: yajun.deng@linux.dev
To: "Yonghong Song" <yhs@fb.com>, "bpf" <bpf@vger.kernel.org>,
"Kumar Kartikeya Dwivedi" <memxor@gmail.com>
Subject: Re: bpf selftest tc_bpf failed with latest bpf-next
Date: Mon, 19 Jul 2021 04:11:15 +0000 [thread overview]
Message-ID: <01896ade8ce4ad062de5cb63a1d09707@linux.dev> (raw)
In-Reply-To: <536141f3-f76a-67d7-a081-c518919efd05@fb.com>
July 19, 2021 3:29 AM, "Yonghong Song" <yhs@fb.com> wrote:
> The bpf selftest tc_bpf failed with latest bpf-next. The following is the command to run and the
> result:
>
> $ ./test_progs -n 132
> [ 40.947571] bpf_testmod: loading out-of-tree module taints kernel.
> test_tc_bpf:PASS:test_tc_bpf__open_and_load 0 nsec
> test_tc_bpf:PASS:bpf_tc_hook_create(BPF_TC_INGRESS) 0 nsec
> test_tc_bpf:PASS:bpf_tc_hook_create invalid hook.attach_point 0 nsec
> test_tc_bpf_basic:PASS:bpf_obj_get_info_by_fd 0 nsec
> test_tc_bpf_basic:PASS:bpf_tc_attach 0 nsec
> test_tc_bpf_basic:PASS:handle set 0 nsec
> test_tc_bpf_basic:PASS:priority set 0 nsec
> test_tc_bpf_basic:PASS:prog_id set 0 nsec
> test_tc_bpf_basic:PASS:bpf_tc_attach replace mode 0 nsec
> test_tc_bpf_basic:PASS:bpf_tc_query 0 nsec
> test_tc_bpf_basic:PASS:handle set 0 nsec
> test_tc_bpf_basic:PASS:priority set 0 nsec
> test_tc_bpf_basic:PASS:prog_id set 0 nsec
> libbpf: Kernel error message: Failed to send filter delete notification
> test_tc_bpf_basic:FAIL:bpf_tc_detach unexpected error: -3 (errno 3)
> test_tc_bpf:FAIL:test_tc_internal ingress unexpected error: -3 (errno 3)
> #132 tc_bpf:FAIL
>
> The failure seems due to the commit
> cfdf0d9ae75b ("rtnetlink: use nlmsg_notify() in rtnetlink_send()")
>
> Without the above commit, rtnetlink_send() will return 0 even if
> netlink_broadcast() (called by rtnetlink_send())
> returns an error. The above commit makes it return
> an error code if netlink_broadcast() failed.
>
> Such a rtnetlink_send() return value change impacted the return value
> for tfilter_del_notify(), in sched/cls_api.c, in the above test.
> Previously return 0, now return -3 (-ESRCH), causing the test failure.
>
> I am not sure what is the proper solution to address this.
> Should we just adjust test, or kernel change is also needed?
Thanks report that, I'll route a patch to fix this in next submit.
>
> Kumar, Yajun, could you take a look?
prev parent reply other threads:[~2021-07-19 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 19:29 bpf selftest tc_bpf failed with latest bpf-next Yonghong Song
2021-07-19 4:11 ` yajun.deng [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=01896ade8ce4ad062de5cb63a1d09707@linux.dev \
--to=yajun.deng@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=yhs@fb.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).