Zenghui Yu 291e4baf70 kselftests: dmabuf-heaps: Ensure the driver name is null-terminated ... Even if a vgem device is configured in, we will skip the import_vgem_fd() test almost every time. TAP version 13 1..11 # Testing heap: system # ======================================= # Testing allocation and importing: ok 1 # SKIP Could not open vgem -1 The problem is that we use the DRM_IOCTL_VERSION ioctl to query the driver version information but leave the name field a non-null-terminated string. Terminate it properly to actually test against the vgem device. While at it, let's check the length of the driver name is exactly 4 bytes and return early otherwise (in case there is a name like "vgemfoo" that gets converted to "vgem\0" unexpectedly). Signed-off-by: Zenghui Yu <yuzenghui@huawei.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: https://patchwork.freedesktop.org/patch/msgid/20240729024604.2046-1-yuzenghui@huawei.com		2024-07-29 09:02:54 +02:00
..
crypto/chacha20-s390
cxl	CXL changes for v6.10 merge window	2024-05-15 14:32:27 -07:00
fault-injection
ktest	ktest: force $buildonly = 1 for 'make_warnings_file' test type	2024-03-15 12:36:19 -04:00
kunit	RISC-V SoC Kconfig Updates for v6.10	2024-05-07 11:02:56 +02:00
memblock
nvdimm	ndtest: Convert to platform remove callback returning void	2024-04-25 12:37:12 -07:00
radix-tree	tools: fix userspace compilation with new test_xarray changes	2024-05-05 17:28:05 -07:00
scatterlist
selftests	kselftests: dmabuf-heaps: Ensure the driver name is null-terminated	2024-07-29 09:02:54 +02:00
vsock