On Mon, 2024-07-08 at 10:29 +0800, Geliang Tang wrote:
> > > > From: Geliang Tang
> > > >
> > > > Include network_helpers.h in prog_tests/sockmap_ktls.c, use
> > > > public
> > > > network
> > > > helper start_server_str() instead of local defined function
> > > > tcp_server().
> > > > This can a
Xu Kuohai writes:
> On 7/5/2024 8:53 PM, Puranjay Mohan wrote:
>> The arm64 bpf JIT currently supports attaching the trampoline to
>> functions with <= 8 arguments. This is because up to 8 arguments can be
>> passed in registers r0-r7. If there are more than 8 arguments then the
>> 9th and later
On 7/8/2024 5:00 PM, Puranjay Mohan wrote:
Xu Kuohai writes:
On 7/5/2024 8:53 PM, Puranjay Mohan wrote:
The arm64 bpf JIT currently supports attaching the trampoline to
functions with <= 8 arguments. This is because up to 8 arguments can be
passed in registers r0-r7. If there are more than 8
On Jul 06 2024, Alexei Starovoitov wrote:
> On Fri, Jul 5, 2024 at 1:54 PM Eduard Zingerman wrote:
> >
> > On Fri, 2024-07-05 at 15:44 +0200, Benjamin Tissoires wrote:
> > > See the previous patch: the API was wrong, we were provided the pointer
> > > to the value, not the actual struct bpf_wq *.
I realized this while having a map containing both a struct bpf_timer and
a struct bpf_wq: the third argument provided to the bpf_wq callback is
not the struct bpf_wq pointer itself, but the pointer to the value in
the map.
Which means that the users need to double cast the provided "value" as
thi
See the previous patch: the API was wrong, we were provided the pointer
to the value, not the actual struct bpf_wq *.
Signed-off-by: Benjamin Tissoires
---
changes in v2:
- amended to retrieve something from the third argument of the callback
---
tools/testing/selftests/bpf/bpf_experimental.h
I realized this while having a map containing both a struct bpf_timer and
a struct bpf_wq: the third argument provided to the bpf_wq callback is
not the struct bpf_wq pointer itself, but the pointer to the value in
the map.
Which means that the users need to double cast the provided "value" as
thi
There are a couple of places where the test script "sleep"s to wait for
some external condition to be met.
This is error prone, specially in slow systems (identified in CI by
"KSFT_MACHINE_SLOW=yes").
To fix this, add a "ovs_wait" function that tries to execute a command
a few times until it succ
Even if a vgem device is configured in, we will skip the import_vgem_fd()
test almost every time.
TAP version 13
1..11
# Testing heap: system
# ===
# Testing allocation and importing:
ok 1 # SKIP Could not open vgem -1
The problem is that we use the
On 7/5/24 4:50 PM, Puranjay Mohan wrote:
fexit_sleep test runs successfully now on the CI so remove it from the
deny list.
Do you happen to know which commit fixed it? If yes, might be nice to have it
documented in the commit message.
Signed-off-by: Puranjay Mohan
---
tools/testing/selftes
Daniel Borkmann writes:
> On 7/5/24 4:50 PM, Puranjay Mohan wrote:
>> fexit_sleep test runs successfully now on the CI so remove it from the
>> deny list.
>
> Do you happen to know which commit fixed it? If yes, might be nice to have it
> documented in the commit message.
Actually, I never saw t
On Mon, Jul 8, 2024 at 5:00 PM Puranjay Mohan wrote:
>
> Daniel Borkmann writes:
>
> > On 7/5/24 4:50 PM, Puranjay Mohan wrote:
> >> fexit_sleep test runs successfully now on the CI so remove it from the
> >> deny list.
> >
> > Do you happen to know which commit fixed it? If yes, might be nice to
On 7/8/24 5:26 PM, KP Singh wrote:
On Mon, Jul 8, 2024 at 5:00 PM Puranjay Mohan wrote:
Daniel Borkmann writes:
On 7/5/24 4:50 PM, Puranjay Mohan wrote:
fexit_sleep test runs successfully now on the CI so remove it from the
deny list.
Do you happen to know which commit fixed it? If yes,
On Mon, Jul 8, 2024 at 5:29 PM Daniel Borkmann wrote:
>
> On 7/8/24 5:26 PM, KP Singh wrote:
> > On Mon, Jul 8, 2024 at 5:00 PM Puranjay Mohan wrote:
> >>
> >> Daniel Borkmann writes:
> >>
> >>> On 7/5/24 4:50 PM, Puranjay Mohan wrote:
> fexit_sleep test runs successfully now on the CI so r
Daniel Borkmann writes:
> On 7/8/24 5:26 PM, KP Singh wrote:
>> On Mon, Jul 8, 2024 at 5:00 PM Puranjay Mohan wrote:
>>>
>>> Daniel Borkmann writes:
>>>
On 7/5/24 4:50 PM, Puranjay Mohan wrote:
> fexit_sleep test runs successfully now on the CI so remove it from the
> deny list.
>>
On 7/8/24 5:35 PM, Puranjay Mohan wrote:
Daniel Borkmann writes:
On 7/8/24 5:26 PM, KP Singh wrote:
On Mon, Jul 8, 2024 at 5:00 PM Puranjay Mohan wrote:
Daniel Borkmann writes:
On 7/5/24 4:50 PM, Puranjay Mohan wrote:
fexit_sleep test runs successfully now on the CI so remove it from t
Hi Maciej,
On 7/4/24 12:23 AM, Maciej Wieczor-Retman wrote:
On 2024-07-03 at 13:51:03 -0700, Reinette Chatre wrote:
On 7/3/24 12:43 AM, Maciej Wieczór-Retman wrote:
On 3.07.2024 00:21, Reinette Chatre wrote:
On 7/1/24 7:18 AM, Maciej Wieczor-Retman wrote:
...
SNC might not be enabled at a
On Mon, Jul 8, 2024 at 6:09 PM Daniel Borkmann wrote:
>
> On 7/8/24 5:35 PM, Puranjay Mohan wrote:
> > Daniel Borkmann writes:
> >
> >> On 7/8/24 5:26 PM, KP Singh wrote:
> >>> On Mon, Jul 8, 2024 at 5:00 PM Puranjay Mohan wrote:
>
> Daniel Borkmann writes:
>
> > On 7/5/24 4:
On Mon, Jul 8, 2024 at 6:47 AM Zenghui Yu wrote:
>
> Even if a vgem device is configured in, we will skip the import_vgem_fd()
> test almost every time.
>
> TAP version 13
> 1..11
> # Testing heap: system
> # ===
> # Testing allocation and importing:
>
Adrian Moreno writes:
> There are a couple of places where the test script "sleep"s to wait for
> some external condition to be met.
>
> This is error prone, specially in slow systems (identified in CI by
> "KSFT_MACHINE_SLOW=yes").
>
> To fix this, add a "ovs_wait" function that tries to execute
On Thu, Jul 4, 2024 at 7:38 PM Geliang Tang wrote:
>
> From: Geliang Tang
>
> Just like handling ENOTSUPP in test_lsm_cgroup_functional(), this patch
> adds a new helper test_progs_get_error() to check whether the input error
> is ENOTSUPP (524) or ENOTSUP (95). If it is, invoke test__skip() to s
On Wed, Jul 3, 2024 at 11:48 PM Geliang Tang wrote:
>
> From: Geliang Tang
>
> There are still some "ENOTSUPP" (-524) errors left when running BPF
> selftests on a Loongarch platform since ASSERT_GE() are used there to
> check the return values, not ASSERT_OK():
>
> '''
> test_bpf_cookie:PASS:sk
On Mon, 2024-07-08 at 10:29 +0800, Geliang Tang wrote:
[...]
> diff --git a/tools/testing/selftests/bpf/network_helpers.h
> b/tools/testing/selftests/bpf/network_helpers.h
> index fcda6b2333ad..14d161d35248 100644
> --- a/tools/testing/selftests/bpf/network_helpers.h
> +++ b/tools/testing/selfte
On Mon, Jul 08, 2024 at 02:27:45PM GMT, Aaron Conole wrote:
> Adrian Moreno writes:
>
> > There are a couple of places where the test script "sleep"s to wait for
> > some external condition to be met.
> >
> > This is error prone, specially in slow systems (identified in CI by
> > "KSFT_MACHINE_SLO
On 7/8/24 15:44, Adrian Moreno wrote:
> There are a couple of places where the test script "sleep"s to wait for
> some external condition to be met.
>
> This is error prone, specially in slow systems (identified in CI by
> "KSFT_MACHINE_SLOW=yes").
>
> To fix this, add a "ovs_wait" function that
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov :
On Mon, 08 Jul 2024 11:52:56 +0200 you wrote:
> I realized this while having a map containing both a struct bpf_timer and
> a struct bpf_wq: the third argument provided to the bpf_wq callback is
> not the struct b
On Fri, 2024-07-05 at 10:38 +0800, Geliang Tang wrote:
[...]
I think that this patch is an improvement independent of the patch-set.
Please submit it separately.
> .../selftests/bpf/prog_tests/bpf_tcp_ca.c| 16
[...]
> @@ -489,6 +494,7 @@ static void test_mixed_links(v
On Mon, 2024-07-08 at 11:54 -0700, Andrii Nakryiko wrote:
> On Thu, Jul 4, 2024 at 7:38 PM Geliang Tang wrote:
> >
> > From: Geliang Tang
> >
> > Just like handling ENOTSUPP in test_lsm_cgroup_functional(), this patch
> > adds a new helper test_progs_get_error() to check whether the input error
On 7/8/24 12:15 PM, Eduard Zingerman wrote:
On Mon, 2024-07-08 at 10:29 +0800, Geliang Tang wrote:
[...]
diff --git a/tools/testing/selftests/bpf/network_helpers.h
b/tools/testing/selftests/bpf/network_helpers.h
index fcda6b2333ad..14d161d35248 100644
--- a/tools/testing/selftests/bpf/network
On Thu, Jul 4, 2024 at 10:57 AM Taehee Yoo wrote:
>
> I found several locking warnings while testing.
>
Thanks for Testing Taehee! And sorry for the late reply. I was off for
a couple of days. With some minor tweaks to my test setup I was able
to reproduce and fix all 3 warnings.
> [ 1135.125874
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann :
On Fri, 5 Jul 2024 14:50:09 + you wrote:
> fexit_sleep test runs successfully now on the CI so remove it from the
> deny list.
>
> Signed-off-by: Puranjay Mohan
> ---
> tools/testing/selftests/bpf/DENYLIST.aar
On 7/7/24 7:29 PM, Geliang Tang wrote:
From: Geliang Tang
EINPROGRESS is skipped in run_lookup_test() in cgroup_skb_sk_lookup
tests, but it is still showed in the log:
./test_progs -t cgroup_skb_sk_lookup -v
run_cgroup_bpf_test:PASS:skel_open_load 0 nsec
run_cgroup_bpf_test:PASS:cgroup_j
On Mon, Jul 08, 2024 at 09:31:58PM GMT, Ilya Maximets wrote:
> On 7/8/24 15:44, Adrian Moreno wrote:
> > There are a couple of places where the test script "sleep"s to wait for
> > some external condition to be met.
> >
> > This is error prone, specially in slow systems (identified in CI by
> > "KS
Hi Linus,
Please pull this kselftest fixes update for Linux 6.10.
This kselftest fixes update for Linux 6.10 consists of fixes to clang
build failures to timerns, vDSO tests and fixes to vDSO makefile.
Note: makefile fixes are included to avoid conflicts during 6.11 merge
window.
diff is attac
Celeste Liu writes:
> Commit 673ce00c5d6c ("ARM: omap2plus_defconfig: Add support for distros
> with systemd") said it's because of recommendation from systemd. But
> systemd changed their recommendation later.[1]
>
> For cgroup v1, if turned on, and there's any cgroup in the "cpu" hierarchy it
>
Geliang Tang wrote:
> From: Geliang Tang
>
> Run this BPF selftests (./test_progs -t sockmap_basic) on a Loongarch
> platform, a kernel panic occurs:
>
> '''
> Oops[#1]:
> CPU: 22 PID: 2824 Comm: test_progs Tainted: G OE 6.10.0-rc2+ #18
> Hardware name: LOONGSON Dabieshan/Loongson-TC5
This patch add three testcases to verify the proper management of
return_instance data by uretprobes:
- uretprobe_longjmp() verifies that longjmp() bypasses the uretprobe BPF
program attached to the exit of instrumented function.
- uretprobe_cleanup_return_instance() verifies that uretprobe rec
While exploring uretprobe syscall and trampoline for ARM64, we observed
a slight performance gain for Redis benchmark using uretprobe syscall.
This patchset aims to further improve the performance of uretprobe by
optimizing the management of struct return_instance data.
In details, uretprobe utili
Reduce the runtime overhead for struct return_instance data managed by
uretprobe. This patch replaces the dynamic allocation with statically
allocated array, leverage two facts that are limited nesting depth of
uretprobe (max 64) and the function call style of return_instance usage
(create at entry
On 2024/7/9 1:49, T.J. Mercier wrote:
On Mon, Jul 8, 2024 at 6:47 AM Zenghui Yu wrote:
>
> Even if a vgem device is configured in, we will skip the import_vgem_fd()
> test almost every time.
>
> TAP version 13
> 1..11
> # Testing heap: system
> # ===
>
40 matches
Mail list logo
