This series introduces a new test that checks for a null pointer dereference that may happen when there is a transport change[1]. This bug was fixed in [2]
First commit introduces a new utility function that checks whether a timeout has expired or not without exiting the test. This is required in the test because timeout expiration does not mean that the test failed. Second commit is the test itself. Note that this test *cannot* fail, it hangs if it triggers a kernel oops. The intended use-case is to run it and then check if there is any oops in the dmesg. This test is based on Michal's python reproducer[3]. [1]https://lore.kernel.org/netdev/Z2LvdTTQR7dBmPb5@v4bel-B760M-AORUS-ELITE-AX/ [2]https://lore.kernel.org/netdev/20250110083511.30419-1-sgarz...@redhat.com/ [3]https://lore.kernel.org/netdev/2b3062e3-bdaa-4c94-a3c0-2930595b9...@rbox.co/ Signed-off-by: Luigi Leonardi <leona...@redhat.com> --- Luigi Leonardi (2): vsock/test: Add new function to check for timeout vsock/test: Add test for null ptr deref when transport changes tools/testing/vsock/Makefile | 1 + tools/testing/vsock/timeout.c | 7 +++- tools/testing/vsock/timeout.h | 3 ++ tools/testing/vsock/vsock_test.c | 80 ++++++++++++++++++++++++++++++++++++++++ 4 files changed, 90 insertions(+), 1 deletion(-) --- base-commit: 848e076317446f9c663771ddec142d7c2eb4cb43 change-id: 20250306-test_vsock-3e77a9c7a245 Best regards, -- Luigi Leonardi <leona...@redhat.com>
