On 10/13/22 20:00, David Hildenbrand wrote:
When did that test start failing? Was it still ok for 6.0?
Didn't test yet, will try, in case it's my system/config specific thing.
So it's actually all the same with v6.0 for me. The infinite loops, the test failures, the misreported SKIPs.
# RUN hmm.hmm_device_private.exclusive ... # hmm-tests.c:1673:exclusive:Expected ret (-16) == 0 (0) hmm close returned (-1) fd is (3) # exclusive: Test failed at step #1 # FAIL hmm.hmm_device_private.exclusive not ok 20 hmm.hmm_device_private.exclusive # RUN hmm.hmm_device_private.exclusive_mprotect ... # hmm-tests.c:1727:exclusive_mprotect:Expected ret (-16) == 0 (0) hmm close returned (-1) fd is (3) # exclusive_mprotect: Test failed at step #1 # FAIL hmm.hmm_device_private.exclusive_mprotect not ok 21 hmm.hmm_device_private.exclusive_mprotect # RUN hmm.hmm_device_private.exclusive_cow ... # hmm-tests.c:1780:exclusive_cow:Expected ret (-16) == 0 (0) hmm close returned (-1) fd is (3) # exclusive_cow: Test failed at step #1 # FAIL hmm.hmm_device_private.exclusive_cow not ok 22 hmm.hmm_device_private.exclusive_cow
Is the kernel compiled with support. I have the feeling that we might simply miss kernel support and it's not handled gracefully ...
If you mean CONFIG_DEVICE_PRIVATE=y then it's there. Couldn't find anything relevant that wouldn't be enabled.