Zenghui Yu d43fde5ebf kselftests: dmabuf-heaps: Ensure the driver name is null-terminated ... [ Upstream commit 291e4baf70 ] 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 Signed-off-by: Sasha Levin <sashal@kernel.org>		2024-09-12 11:11:38 +02:00
..
crypto/chacha20-s390
cxl	cxl/region: check interleave capability	2024-07-05 09:34:07 +02:00
fault-injection
ktest	ktest: force $buildonly = 1 for 'make_warnings_file' test type	2024-04-13 13:07:37 +02:00
kunit	kunit: tool: fix parsing of test attributes	2024-02-05 20:14:15 +00:00
memblock
nvdimm
radix-tree	maple_tree: do not preallocate nodes for slot stores	2024-01-05 15:19:43 +01:00
scatterlist
selftests	kselftests: dmabuf-heaps: Ensure the driver name is null-terminated	2024-09-12 11:11:38 +02:00
vsock	vsock/test: fix SEQPACKET message bounds test	2023-12-03 07:33:05 +01:00