[BUG] selftests: memfd: run_hugetlbfs_test.sh: Hang in fuse_mnt?

2024-01-06 Thread Mirsad Todorovac
Hi all, I'm running the 6.7.0-rc8-00174-g95c8a35f1c01 kernel from torvalds tree on a Ubuntu 23.10 Mantic Minotaur system. What I get are these errors. memfd selftests are actually counted as "ok", but they give errors and/or hang. Please find the strace output attached, and the config used.

[PATCH v1 1/1] selftests: net: increase timeout value for tests

2024-01-06 Thread Mirsad Todorovac
In particular, fcnal-test.sh timed out on slower hardware after some new permutations of tests were added. This single test ran for almost an hour instead of the expected 25 min (1500s). 75 minutes should suffice for most systems. Cc: David Ahern Cc: "David S. Miller" Cc: Eric Dumazet Cc:

Re: selftest: net: fcnal-test.sh TIMEOUT

2024-01-06 Thread Mirsad Todorovac
On 06. 01. 2024. 22:02, Mirsad Todorovac wrote: > On 06. 01. 2024. 17:16, David Ahern wrote: >> On 1/5/24 2:41 AM, Mirsad Todorovac wrote: >>> diff --git a/tools/testing/selftests/net/settings >>> b/tools/testing/selftests/net/settings index dfc27cdc6c05..ed8418e8217a >>> 100644 ---

[BUG] selftests: alsa: conf.c: wrong parm passed to printf [FIXED]

2024-01-06 Thread Mirsad Todorovac
Hi, all, There is a minor omission in selftests/alsa/conf.c, returning errno where there is strerror(errno) passed in the sibling calls to printf(). The bug was apparently introduced with the commit aba51cd0949ae ("selftests: alsa - add PCM test"). As a diff speaks like a thousand words, the

Re: selftest: net: fcnal-test.sh TIMEOUT

2024-01-06 Thread Mirsad Todorovac
On 06. 01. 2024. 17:16, David Ahern wrote: > On 1/5/24 2:41 AM, Mirsad Todorovac wrote: >> diff --git a/tools/testing/selftests/net/settings >> b/tools/testing/selftests/net/settings index dfc27cdc6c05..ed8418e8217a >> 100644 --- a/tools/testing/selftests/net/settings +++ >>

Re: [PATCH bpf-next v2 3/3] bpf: treewide: Annotate BPF kfuncs in BTF

2024-01-06 Thread Jiri Olsa
On Fri, Jan 05, 2024 at 09:55:43AM -0700, Daniel Xu wrote: > On Fri, Jan 05, 2024 at 04:11:33PM +0100, Jiri Olsa wrote: > > On Thu, Jan 04, 2024 at 07:45:49PM -0700, Daniel Xu wrote: > > > > SNIP > > > > > diff --git a/fs/verity/measure.c b/fs/verity/measure.c > > > index

[PATCH bpf-next v3 3/3] bpf: treewide: Annotate BPF kfuncs in BTF

2024-01-06 Thread Daniel Xu
This commit marks kfuncs as such inside the .BTF_ids section. The upshot of these annotations is that we'll be able to automatically generate kfunc prototypes for downstream users. The process is as follows: 1. In source, use BTF_KFUNCS_START/END macro pair to mark kfuncs 2. During build, pahole

[PATCH bpf-next v3 0/3] Annotate kfuncs in .BTF_ids section

2024-01-06 Thread Daniel Xu
=== Description === This is a bpf-treewide change that annotates all kfuncs as such inside .BTF_ids. This annotation eventually allows us to automatically generate kfunc prototypes from bpftool. We store this metadata inside a yet-unused flags field inside struct btf_id_set8 (thanks Kumar!).

Re: selftest: net: fcnal-test.sh TIMEOUT

2024-01-06 Thread David Ahern
On 1/5/24 2:41 AM, Mirsad Todorovac wrote: > diff --git a/tools/testing/selftests/net/settings > b/tools/testing/selftests/net/settings index dfc27cdc6c05..ed8418e8217a > 100644 --- a/tools/testing/selftests/net/settings +++ > b/tools/testing/selftests/net/settings @@ -1 +1 @@ -timeout=1500 >

[PATCH 1/1] KVM: selftests: add kvmclock drift test

2024-01-06 Thread Dongli Zhang
There is kvmclock drift issue during the vCPU hotplug. It has been fixed by the commit c52ffadc65e2 ("KVM: x86: Don't unnecessarily force masterclock update on vCPU hotplug"). This is to add the test to verify if the master clock is updated when we write 0 to MSR_IA32_TSC from the host side.