lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: 
 <171389283161.853.7024600173174384381.git-patchwork-notify@kernel.org>
Date: Tue, 23 Apr 2024 17:20:31 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 pabeni@...hat.com, shuah@...nel.org, petrm@...dia.com,
 linux-kselftest@...r.kernel.org, willemdebruijn.kernel@...il.com
Subject: Re: [PATCH net-next v5 0/7] selftests: drv-net: support testing with a
 remote system

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Fri, 19 Apr 2024 19:52:30 -0700 you wrote:
> Hi!
> 
> Implement support for tests which require access to a remote system /
> endpoint which can generate traffic.
> This series concludes the "groundwork" for upstream driver tests.
> 
> I wanted to support the three models which came up in discussions:
>  - SW testing with netdevsim
>  - "local" testing with two ports on the same system in a loopback
>  - "remote" testing via SSH
> so there is a tiny bit of an abstraction which wraps up how "remote"
> commands are executed. Otherwise hopefully there's nothing surprising.
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/7] selftests: drv-net: define endpoint structures
    https://git.kernel.org/netdev/net-next/c/1a20a9a0ddef
  - [net-next,v5,2/7] selftests: drv-net: factor out parsing of the env
    https://git.kernel.org/netdev/net-next/c/543389295085
  - [net-next,v5,3/7] selftests: drv-net: construct environment for running tests which require an endpoint
    https://git.kernel.org/netdev/net-next/c/1880f272d2f9
  - [net-next,v5,4/7] selftests: drv-net: add a trivial ping test
    https://git.kernel.org/netdev/net-next/c/a48a87c08664
  - [net-next,v5,5/7] selftests: net: support matching cases by name prefix
    https://git.kernel.org/netdev/net-next/c/01b431641c33
  - [net-next,v5,6/7] selftests: drv-net: add a TCP ping test case (and useful helpers)
    https://git.kernel.org/netdev/net-next/c/31611cea8f0f
  - [net-next,v5,7/7] selftests: drv-net: add require_XYZ() helpers for validating env
    https://git.kernel.org/netdev/net-next/c/f1e68a1a4a40

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ