From: Yuan Chen
This patch identifies whether a test item is valid by adding a valid flag to
res.
When we test the bpf_cookies/perf_event sub-test item of test_progs, there is a
probability failure of the test item. In fact, this is not a problem, because
the corresponding perf event is not col
Jakub Kicinski wrote:
> On Fri, 30 Aug 2024 14:47:43 -0400 Willem de Bruijn wrote:
> > > We have directories in net/lib, and it's a target, and it works, no?
> >
> > net/lib is not a TARGET in tools/testing/selftests/Makefile. Its
> > Makefile only generates dependencies for other targets: TEST_
kselftest/next kselftest-lkdtm: 2 runs, 1 regressions
(v6.11-rc1-18-gf0a6ecebd8586)
Regressions Summary
---
platform| arch | lab | compiler | defconfig
| regressions
+--+-+--+-
kselftest/next kselftest-seccomp: 2 runs, 3 regressions
(v6.11-rc1-18-gf0a6ecebd8586)
Regressions Summary
---
platform | arch | lab | compiler | defconfig
| regressions
-+---+-+--
kselftest/next kselftest-lib: 2 runs, 1 regressions
(v6.11-rc1-18-gf0a6ecebd8586)
Regressions Summary
---
platform| arch | lab | compiler | defconfig
| regressions
+--+-+--+---
From: Willem de Bruijn
Lay the groundwork to import into kselftests the over 150 packetdrill
TCP/IP conformance tests on github.com/google/packetdrill.
Florian recently added support for packetdrill tests in nf_conntrack,
in commit a8a388c2aae49 ("selftests: netfilter: add packetdrill based
conn
From: Willem de Bruijn
Support testcases that are themselves not executable, but need an
interpreter to run them.
If a test file is not executable, but an executable file
ksft_runner.sh exists in the TARGET dir, kselftest will run
./ksft_runner.sh ./$BASENAME_TEST
Packetdrill may add hundr
From: Willem de Bruijn
Lay the groundwork to import into kselftests the over 150 packetdrill
TCP/IP conformance tests on github.com/google/packetdrill.
1/2: add kselftest infra for TEST_PROGS that need an interpreter
2/2: add the specific packetdrill tests
Both can go through net-next, I imagi
kselftest/next build: 7 builds: 2 failed, 5 passed, 1 warning
(v6.11-rc1-18-gf0a6ecebd8586)
Full Build Summary:
https://kernelci.org/build/kselftest/branch/next/kernel/v6.11-rc1-18-gf0a6ecebd8586/
Tree: kselftest
Branch: next
Git Describe: v6.11-rc1-18-gf0a6ecebd8586
Git Commit: f0a6ecebd858658
On Thu, Sep 5, 2024 at 5:16 AM Willem de Bruijn
wrote:
>
> Jason Xing wrote:
> > From: Jason Xing
> >
> > When I was trying to modify the tx timestamping feature, I found that
> > running "./txtimestamp -4 -C -L 127.0.0.1" didn't reflect the fact
> > properly.
>
> Did not reflect what fact? Sorry
Hi Linus,
Please pull the following KUnit fixes update for Linux 6.11-rc7.
This kunit update for Linux 6.11-rc7 consist of one single fix to
a use-after-free bug resulting from kunit_driver_create() failing
to copy the driver name leaving it on the stack or freeing it.
diff is attached.
thanks
On Thu, 29 Aug 2024 at 11:32, Michal Wajdeczko
wrote:
>
> While kunit/visibility.h is today not included in any generated
> kernel documentation, also likely due to the fact that none of the
> existing comments are correctly recognized as kernel-doc, but once
> we decide to add this header and fix
Jason Xing wrote:
> From: Jason Xing
>
> When I was trying to modify the tx timestamping feature, I found that
> running "./txtimestamp -4 -C -L 127.0.0.1" didn't reflect the fact
> properly.
Did not reflect what fact? Sorry, I don't entirely follow the issue
you raise.
> In this selftest file,
On Mon, Sep 2, 2024 at 1:19 AM Tony Ambardar wrote:
>
> On Fri, Aug 30, 2024 at 02:14:19PM -0700, Andrii Nakryiko wrote:
> > On Fri, Aug 30, 2024 at 12:30 AM Tony Ambardar
> > wrote:
> > >
> > > Support for handling BTF data of either endianness was added in [1], but
> > > did not include BTF.ex
On Tue, Sep 3, 2024 at 12:34 AM Tony Ambardar wrote:
>
> Allow static linking object files of either endianness, checking that input
> files have consistent byte-order, and setting output endianness from input.
>
> Linking requires in-memory processing of programs, relocations, sections,
> etc. in
On Tue, Sep 3, 2024 at 12:33 AM Tony Ambardar wrote:
>
> Allow bpf_object__open() to access files of either endianness, and convert
> included BPF programs to native byte-order in-memory for introspection.
> Loading BPF objects of non-native byte-order is still disallowed however.
>
> Signed-off-b
On Tue, Sep 3, 2024 at 12:33 AM Tony Ambardar wrote:
>
> Support for handling BTF data of either endianness was added in [1], but
> did not include BTF.ext data for lack of use cases. Later, support for
> static linking [2] provided a use case, but this feature and later ones
> were restricted to
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov :
On Tue, 3 Sep 2024 09:28:39 +0800 you wrote:
> From: Yuan Chen
>
> When the PROCMAP_QUERY is not defined, a compilation error occurs due to the
> mismatch of the procmap_query()'s params, procmap_query() only be
On Wed, 04 Sep 2024 17:17:58 +0100,
Will Deacon wrote:
>
> On Wed, Sep 04, 2024 at 01:55:03PM +0100, Joey Gouly wrote:
> > On Wed, Sep 04, 2024 at 12:43:02PM +0100, Will Deacon wrote:
> > > Right, there's quite a lot I need to do:
> > >
> > > - Uncorrupt your patches
> > > - Fix the conflict in
On Wed, Sep 04, 2024 at 01:55:03PM +0100, Joey Gouly wrote:
> On Wed, Sep 04, 2024 at 12:43:02PM +0100, Will Deacon wrote:
> > Right, there's quite a lot I need to do:
> >
> > - Uncorrupt your patches
> > - Fix the conflict in the kvm selftests
> > - Drop the unnecessary ISBs
> > - Fix the ESR che
From: Jason Xing
When I was trying to modify the tx timestamping feature, I found that
running "./txtimestamp -4 -C -L 127.0.0.1" didn't reflect the fact
properly.
In this selftest file, we respectively test three tx generation flags.
With the generation and report flag enabled, we expect that t
On Wed, Sep 04, 2024 at 12:43:02PM +0100, Will Deacon wrote:
> On Wed, Sep 04, 2024 at 12:32:21PM +0100, Joey Gouly wrote:
> > On Wed, Sep 04, 2024 at 11:22:54AM +0100, Will Deacon wrote:
> > > On Tue, Sep 03, 2024 at 03:54:13PM +0100, Joey Gouly wrote:
> > > > On Mon, Sep 02, 2024 at 08:08:08PM +0
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller :
On Tue, 3 Sep 2024 00:06:10 +0800 you wrote:
> From: Jason Xing
>
> Add the SO_PEEK_OFF selftest for UDP. In this patch, I mainly do
> three things:
> 1. rename tcp_so_peek_off.c
> 2. adjust for UDP protocol
> 3.
On Wed, Sep 04, 2024 at 12:32:21PM +0100, Joey Gouly wrote:
> On Wed, Sep 04, 2024 at 11:22:54AM +0100, Will Deacon wrote:
> > On Tue, Sep 03, 2024 at 03:54:13PM +0100, Joey Gouly wrote:
> > > On Mon, Sep 02, 2024 at 08:08:08PM +0100, Catalin Marinas wrote:
> > > > On Tue, Aug 27, 2024 at 12:38:04P
On Wed, Sep 04, 2024 at 11:22:54AM +0100, Will Deacon wrote:
> On Tue, Sep 03, 2024 at 03:54:13PM +0100, Joey Gouly wrote:
> > commit 3141fb86bee8d48ae47cab1594dad54f974a8899
> > Author: Joey Gouly
> > Date: Tue Sep 3 15:47:26 2024 +0100
> >
> > fixup! arm64: context switch POR_EL0 register
On Wed, Sep 04, 2024 at 11:22:54AM +0100, Will Deacon wrote:
> On Tue, Sep 03, 2024 at 03:54:13PM +0100, Joey Gouly wrote:
> > On Mon, Sep 02, 2024 at 08:08:08PM +0100, Catalin Marinas wrote:
> > > On Tue, Aug 27, 2024 at 12:38:04PM +0100, Will Deacon wrote:
> > > > On Fri, Aug 23, 2024 at 07:40:52
On Tue, Sep 03, 2024 at 03:54:13PM +0100, Joey Gouly wrote:
> On Mon, Sep 02, 2024 at 08:08:08PM +0100, Catalin Marinas wrote:
> > On Tue, Aug 27, 2024 at 12:38:04PM +0100, Will Deacon wrote:
> > > On Fri, Aug 23, 2024 at 07:40:52PM +0100, Catalin Marinas wrote:
> > > > On Fri, Aug 23, 2024 at 06:0
27 matches
Mail list logo
