From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Christian_K=c3=b6nig?= Subject: Re: KASAN use-after-free report during piglit run Date: Wed, 25 Oct 2017 17:51:30 +0200 Message-ID: References: Reply-To: christian.koenig-5C7GfCeVMHo@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2119625592==" Return-path: In-Reply-To: Content-Language: en-US List-Id: Discussion list for AMD gfx List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: amd-gfx-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "amd-gfx" To: =?UTF-8?Q?Michel_D=c3=a4nzer?= , amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org This is a multi-part message in MIME format. --===============2119625592== Content-Type: multipart/alternative; boundary="------------0719DE9E814DF0ECCE27F0EA" Content-Language: en-US This is a multi-part message in MIME format. --------------0719DE9E814DF0ECCE27F0EA Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Going to take a look tomorrow. Christian. Am 25.10.2017 um 17:43 schrieb Michel Dänzer: > KASAN caught another use-after-free on my development machine today, see > the attached dmesg excerpt. There haven't been any related changes in > amd-staging-drm-next since yesterday, so maybe userspace is just > tickling the kernel differently (e.g. piglit runs some more tests in > parallel now). It's not reproducible every time, but it just happened a > second time (with an amd-staging-drm-next commit from about a week ago). > > > > > _______________________________________________ > amd-gfx mailing list > amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org > https://lists.freedesktop.org/mailman/listinfo/amd-gfx --------------0719DE9E814DF0ECCE27F0EA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
Going to take a look tomorrow.

Christian.

Am 25.10.2017 um 17:43 schrieb Michel Dänzer:
KASAN caught another use-after-free on my development machine today, see
the attached dmesg excerpt. There haven't been any related changes in
amd-staging-drm-next since yesterday, so maybe userspace is just
tickling the kernel differently (e.g. piglit runs some more tests in
parallel now). It's not reproducible every time, but it just happened a
second time (with an amd-staging-drm-next commit from about a week ago).





_______________________________________________
amd-gfx mailing list
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx


--------------0719DE9E814DF0ECCE27F0EA-- --===============2119625592== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KYW1kLWdmeCBt YWlsaW5nIGxpc3QKYW1kLWdmeEBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9hbWQtZ2Z4Cg== --===============2119625592==--