| 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
| ||
|
Message-ID: <20240412180428.35b83923@kernel.org> Date: Fri, 12 Apr 2024 18:04:28 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Jiri Pirko <jiri@...nulli.us> Cc: netdev@...r.kernel.org, pabeni@...hat.com, davem@...emloft.net, edumazet@...gle.com, parav@...dia.com, mst@...hat.com, jasowang@...hat.com, xuanzhuo@...ux.alibaba.com, shuah@...nel.org, petrm@...dia.com, liuhangbin@...il.com, vladimir.oltean@....com, bpoirier@...dia.com, idosch@...dia.com, virtualization@...ts.linux.dev Subject: Re: [patch net-next 0/6] selftests: virtio_net: introduce initial testing infrastructure On Fri, 12 Apr 2024 17:13:08 +0200 Jiri Pirko wrote: > This patchset aims at introducing very basic initial infrastructure > for virtio_net testing, namely it focuses on virtio feature testing. > > The first patch adds support for debugfs for virtio devices, allowing > user to filter features to pretend to be driver that is not capable > of the filtered feature. Two trivial points: MAINTAINERS should probably be updated to bestow the responsibility over these to virtio folks; there should probably be a config file. Admittedly anyone testing in a VM should have VIRTIO and anyone not in a VM won't test this... but it's a good practice. Did you investigate how hard it would be to make virtme-ng pop out two virtio interfaces? It's a pretty hackable Python code base and Andrea is very responsive so would be nice to get that done. And then its trivial to run those in our CI.
Powered by blists - more mailing lists