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

[Alex Deucher <alexdeucher@gmail.com>]

On Wed, Feb 21, 2024 at 9:13 AM Christian König
<christian.koenig@amd.com> wrote:
>
> Am 20.02.24 um 18:43 schrieb Erhard Furtner:
> > On Tue, 20 Feb 2024 14:50:04 +0100
> > Christian König <christian.koenig@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?

Makes sense to me.

Acked-by: Alex Deucher <alexander.deucher@amd.com>

>
> Thanks,
> Christian.
>
> >
> > Regards,
> > Erhard