Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

[Christian König]

Am 20.02.24 um 18:43 schrieb Erhard Furtner:
> On Tue, 20 Feb 2024 14:50:04 +0100
> Christian König <christian.koenig at amd.com> wrote:
>
>> Yeah and that's probably the problem. The test is not supposed to be
>> compiled and executed on bare metal, but rather just as unit test
>> through user mode Linux.
>>
>> We probably don't check that correctly in the kconfig for some reason.
>> Can you provide your .config file?
>>
> Here's my v6.8-rc5 .config attached.

Thanks for that.

As long as nobody comes up with an approach how to run the test even 
when other drivers want to interact with TTM the attached patch is my 
best idea.

It basically disabled compiling the TTM tests as long as neither 
compiling for UML or COMPILE_TEST are set.

Opinions?

Thanks,
Christian.

>
> Regards,
> Erhard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-drm-ttm-tests-depend-on-UML-COMPILE_TEST.patch
Type: text/x-patch
Size: 1604 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20240221/dd4d0ee0/attachment.bin>