Hi,
Thank you for patching two of the bugs we have reported!
I was just wondering if there's any news on the one other bug we have
reported:
BUG: KASAN: slab-use-after-free in amdgpu_bo_move+0x1479/0x1550.
I see that there is a gitlab issue(
https://gitlab.freedesktop.org/drm/amd/-/issues/3171) c
Hi guys,
yeah that is a well known issue but actually completely harmless.
What happens is that a trace function accesses a stale pointer to print
some additional value into the trace log.
That memory might have been reused and the information is now outdated,
but the worst thing that can ha
Hello,
thank you for patching the first bug we have sent!
Just a quick touch base with you, to ask if there has been any update on
our other two bugs.
They were each sent with emails titled
"Reporting a slab-use-after-free in amdgpu" (this one)
"Reporting a null-ptr-deref in amdgpu".
Thank you!
Hi Vitaly,
No worries, thank you for working on the patches!
I have also confirmed that with the inflight patch, issue No.1
(use-after-free) seems to be resolved.
However, I have reproduced issue No.3 (slab-use-after-free) even with the
patch for issue No.1 applied - if it's the first program tes
Hi Joonkyo,
Sorry for the delay.
Yes, sure, I reproduced issue 2 (null-ptr-deref in amdgpu) and I will provide
the fix soon.
However, issue No. 3 is no longer reproducible if the recent patch inflight is
applied which fixes issue No 1.
Do you see the same behavior?
Thanks in advance, Vitaly
On
