Re: [PATCH] selftests: core: include linux/close_range.h for CLOSE_RANGE_* macros

Kind reminder On 12/11/23 4:01 PM, Muhammad Usama Anjum wrote: > Soft reminder > > On 11/29/23 4:34 PM, Muhammad Usama Anjum wrote: >> Soft reminder >> >> On 10/24/23 8:51 PM, Muhammad Usama Anjum wrote: >>> Correct header file is needed for getting CLOSE_RANGE_* macros. >>> Previously it was tes

selftest: net: fcnal-test.sh TIMEOUT

Hi, all, The default timeout for tools/testing/selftest/net groups of tests is 1500s (25m). This is less than half of what is required to run the full fcnal-test.sh on my hardware (53m48s). With the timeout adjusted, tests passed 914 of 914 OK. Best regards, Mirsad Todorovac diff --git a/to

Re: [RFC PATCH v2 2/3] KVM: selftests: add selftest driver for KVM to test memory slots for MMIO BARs

On Thu, Jan 04, 2024 at 04:16:04PM +0800, Yuan Yao wrote: > On Wed, Jan 03, 2024 at 04:44:57PM +0800, Yan Zhao wrote: > > This driver is for testing KVM memory slots for device MMIO BARs that are > > mapped to pages serving as device resources. > > > > This driver implements a mock device whose dev

Re: [RFC PATCH v2 3/3] KVM: selftests: Add set_memory_region_io to test memslots for MMIO BARs

On Fri, Jan 05, 2024 at 02:25:26PM +0800, Yuan Yao wrote: > On Wed, Jan 03, 2024 at 04:45:35PM +0800, Yan Zhao wrote: > > Added a selftest set_memory_region_io to test memslots for MMIO BARs. > > Emm.. "set_memory_region_io" doesn't represent the real testing purpose, > but not sure if things like

[PATCH v4 8/8] selftests/pcie_bwctrl: Create selftests

Create selftests for PCIe BW control through the PCIe cooling device sysfs interface. First, the BW control selftest finds the PCIe Port to test with. By default, the PCIe Port with the highest Link Speed is selected but another PCIe Port can be provided with -d parameter. The actual test steps t

Re: [PATCH v7 1/3] iommufd: Add data structure for Intel VT-d stage-1 cache invalidation

On Fri, Jan 05, 2024 at 02:52:50AM +, Tian, Kevin wrote: > > but in reality the relation could be identified in an easy way due to a SIOV > > restriction which we discussed before - shared PASID space of PF disallows > > assigning sibling vdev's to a same VM (otherwise no way to identify which

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

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 bf7a5f4cccaf..3969d54158d1 100644 > --- a/fs/verity/measure.c > +++ b/fs/verity/measure.c > @@ -159,9 +159,9 @@ __bpf_kfunc int bpf_get_fsverity_digest(struct file > *

Re: [PATCH bpf-next v2 0/3] Annotate kfuncs in .BTF_ids section

On Thu, Jan 04, 2024 at 07:45:46PM -0700, Daniel Xu wrote: > === 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

Re: [PATCH v7 1/3] iommufd: Add data structure for Intel VT-d stage-1 cache invalidation

On Thu, Jan 04, 2024 at 11:38:40PM -0800, Nicolin Chen wrote: > On Wed, Jan 03, 2024 at 08:02:04PM -0400, Jason Gunthorpe wrote: > > On Wed, Jan 03, 2024 at 12:18:35PM -0800, Nicolin Chen wrote: > > > > The driver would have to create it and there would be some driver > > > > specific enclosing str

[PATCH 0/1] selftest/mm/hugetlb: SIGBUS on stolen page

This test case triggers a race between madvise(MADV_DONTNEED) and mmap() in a single huge page, which got stolen (while reserved). Once the only page is stolen, the memory previously mmaped (and madvise(MADV_DONTNEED) got a SIGBUS when accessed. I am not adding this test to the un_vmtests.sh scri

[PATCH 1/1] selftests/mm: new test that steals pages

This test stresses the race between of madvise(DONTNEED), a page fault and a parallel huge page mmap, which should fail due to lack of available page available for mapping. This test case must run on a system with one and only one huge page available. # echo 1 > /sys/kernel/mm/hugepages/h

Re: [PATCH net-next v3 0/3] net: gro: reduce extension header parsing overhead

Hello: This series was applied to netdev/net-next.git (main) by Jakub Kicinski : On Wed, 3 Jan 2024 15:36:41 +0100 you wrote: > This series attempts to reduce the parsing overhead of IPv6 extension > headers in GRO and GSO, by removing extension header specific code and > enabling the frag0 fast

Re: [PATCH 0/1] selftest/mm/hugetlb: SIGBUS on stolen page

On Fri, 5 Jan 2024 07:54:18 -0800 Breno Leitao wrote: > This test case triggers a race between madvise(MADV_DONTNEED) and > mmap() in a single huge page, which got stolen (while reserved). > > Once the only page is stolen, the memory previously mmaped (and > madvise(MADV_DONTNEED) got a SIGBUS

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

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 bf7a5f4cccaf..3969d54158d1 100644 > > --- a/fs/verity/measure.c > > +++ b/fs/verity/measure.c > >

Re: [PATCH 0/1] selftest/mm/hugetlb: SIGBUS on stolen page

On Fri, Jan 05, 2024 at 08:42:38AM -0800, Andrew Morton wrote: > On Fri, 5 Jan 2024 07:54:18 -0800 Breno Leitao wrote: > > > This test case triggers a race between madvise(MADV_DONTNEED) and > > mmap() in a single huge page, which got stolen (while reserved). > > > > Once the only page is stole

Re: [PATCH bpf-next 12/15] bpf: Preserve boundaries and track scalars on narrowing fill

On Thu, 04 Jan 2024 at 04:27:00 +0200, Eduard Zingerman wrote: > On Wed, 2023-12-20 at 23:40 +0200, Maxim Mikityanskiy wrote: > > [...] > > The two tests below were added by the following commit: > ef979017b837 ("bpf: selftest: Add verifier tests for <8-byte scalar spill and > refill") > > As f

Re: [PATCH 0/1] selftest/mm/hugetlb: SIGBUS on stolen page

On Fri, 2024-01-05 at 08:42 -0800, Andrew Morton wrote: > On Fri,  5 Jan 2024 07:54:18 -0800 Breno Leitao > wrote: > > > This test case triggers a race between madvise(MADV_DONTNEED) and > > mmap() in a single huge page, which got stolen (while reserved). > > > > Once the only page is stolen, th

Re: [RFC PATCH v4 4/4] mseal:add documentation

On Thu, Jan 4, 2024 at 3:47 PM Randy Dunlap wrote: > > > > On 1/4/24 10:51, jef...@chromium.org wrote: > > From: Jeff Xu > > > > Add documentation for mseal(). > > > > Signed-off-by: Jeff Xu > > --- > > Documentation/userspace-api/mseal.rst | 181 ++ > > 1 file changed,

Re: [RFC PATCH v4 1/4] mseal: Wire up mseal syscall

On Thu, Jan 4, 2024 at 11:44 PM Greg KH wrote: > > On Thu, Jan 04, 2024 at 06:51:34PM +, jef...@chromium.org wrote: > > From: Jeff Xu > > > > Wire up mseal syscall for all architectures. > > > > Signed-off-by: Jeff Xu > > Doesn't this break the build at this point in the patch series? > Yes.

Re: [PATCH v3] kunit: run test suites only after module initialization completes

On Wed, Dec 6, 2023 at 10:07 AM Marco Pagani wrote: > > Commit 2810c1e99867 ("kunit: Fix wild-memory-access bug in > kunit_free_suite_set()") fixed a wild-memory-access bug that could have > happened during the loading phase of test suites built and executed as > loadable modules. However, it also

Re: [PATCH net-next] selftests: forwarding: Avoid failures to source net/lib.sh

Hello: This patch was applied to netdev/net-next.git (main) by Jakub Kicinski : On Thu, 4 Jan 2024 09:11:09 -0500 you wrote: > The expression "source ../lib.sh" added to net/forwarding/lib.sh in commit > 25ae948b4478 ("selftests/net: add lib.sh") does not work for tests outside > net/forwarding